chore: release v1.5.0 #725
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
WalkthroughThe recent update to version 1.5.0 of the file uploader project introduces key enhancements, including a critical bug fix for a memory leak in the cloud image editor, improving resource management. The update also adds accessibility features for users with assistive technologies and expands the public upload API with a new method, Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (3)
- CHANGELOG.md (1 hunks)
- env.js (1 hunks)
- package.json (1 hunks)
Files skipped from review due to trivial changes (2)
- env.js
- package.json
Additional context used
Markdownlint
CHANGELOG.md
3-3: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time(MD001, heading-increment)
Additional comments not posted (1)
CHANGELOG.md (1)
1-11: Changelog entries approved.The entries for version 1.5.0 accurately reflect the changes described in the PR summary and AI-generated summary, including bug fixes and new features.
Tools
Markdownlint
3-3: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time(MD001, heading-increment)
| @@ -1,3 +1,15 @@ | |||
| # [1.5.0](https://github.com/uploadcare/file-uploader/compare/v1.4.0...v1.5.0) (2024-08-15) | |||
|
|
|||
| ### Bug Fixes | |||
There was a problem hiding this comment.
Fix heading level increment.
The heading level for "Bug Fixes" should be adjusted to ensure proper increment from the previous heading level.
- ### Bug Fixes
+ ## Bug FixesCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Bug Fixes | |
| ## Bug Fixes |
Tools
Markdownlint
3-3: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time(MD001, heading-increment)
This pull request prepares the following release:
1.4.0→1.5.0Release Summary
This is going to be published with the following command:
npm publish --tag latest --access publicMerging Instructions
When merging this pull request, you need to Squash and merge and make sure that the title starts with
chore: release v1.5.0.See details
After that, a commit
chore: release v1.5.0will be added and you or your CI can runshipjs triggerto trigger the release based on the commit.This pull request is automatically generated by Ship.js.
Summary by CodeRabbit
New Features
Bug Fixes
Chores