chore: release v1.6.0

[github-actions]

This pull request prepares the following release:

Repository	Branch	Update	Change
file-uploader	releases/v1.6.0	minor	1.5.2 → 1.6.0

Release Summary

This is going to be published with the following command:

npm publish --tag latest --access public

Merging Instructions

When merging this pull request, you need to Squash and merge and make sure that the title starts with chore: release v1.6.0.

See details

After that, a commit chore: release v1.6.0 will be added and you or your CI can run shipjs trigger to trigger the release based on the commit.

---

This pull request is automatically generated by Ship.js.

Summary by CodeRabbit

• New Features

  • Introduced an event listener to enhance accessibility for file uploads.

• Bug Fixes

  • Corrected the npm version link in the documentation.

• Chores

  • Updated version number to 1.6.0 in the project documentation and configuration files.

[coderabbitai]

Walkthrough

The changes primarily involve updating the version number of the file uploader project from 1.5.2 to 1.6.0 across multiple files. A bug fix is documented in the CHANGELOG.md, correcting the npm version link, while a new feature enhancing accessibility is introduced. The PACKAGE_VERSION constant in env.js and the version in package.json are both updated to reflect this new version.

Changes

File	Change Summary
CHANGELOG.md	Updated for version 1.6.0; documented bug fix and new accessibility feature.
env.js	Updated PACKAGE_VERSION from '1.5.2' to '1.6.0'.
package.json	Updated version from "1.5.2" to "1.6.0".

Poem

In the meadow, changes bloom,
A version new, dispelling gloom.
With links corrected, features bright,
Accessibility takes flight!
Hoppy days are here to stay,
Let's celebrate the coder's way! 🐰✨

---

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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 649db3b and 5eb7bbf.

Files ignored due to path filters (1)

• package-lock.json is 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 (2)

CHANGELOG.md (2)

3-5: LGTM!

The bug fix documentation is correct.

Tools

Markdownlint

3-3: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time

(MD001, heading-increment)

---

7-9: LGTM!

The feature documentation is correct.