Version Packages

[Sec-ant]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• 1a9a372: Bump zxing-cpp to 579650a to fix incorrect PDF417 position info.

Summary by CodeRabbit

• New Features

  • Updated to version 1.3.4, enhancing the functionality of PDF417 information positioning.

• Bug Fixes

  • Addressed an issue with incorrect PDF417 position information.
  • Previous updates improved DataBar detection rates and fixed ITF detection regressions.

• Documentation

  • Updated changelog to reflect the latest version and document previous improvements.

[coderabbitai]

Walkthrough

The changes in this pull request include the deletion of a patch note file that documented an update to the zxing-wasm package, specifically updating the zxing-cpp version to 579650a to fix PDF417 positioning issues. Additionally, the CHANGELOG.md was updated to reflect the new version 1.3.4, which includes this patch. The package.json file was also modified to update the version number from 1.3.3 to 1.3.4, with no other changes made to the file structure.

Changes

File	Change Summary
.changeset/curly-houses-bathe.md	Deleted file containing a patch note for updating zxing-cpp to version 579650a.
CHANGELOG.md	Updated to include version 1.3.4 with details of the zxing-cpp update for PDF417 positioning.
package.json	Version updated from 1.3.3 to 1.3.4.

Possibly related PRs

• chore: bump zxing-cpp to d0c1f34 and add pkg.pr.new #103: Involves bumping the zxing-cpp dependency, directly related to the main PR.
• Version Packages #105: Includes a patch that bumps the zxing-cpp dependency, indicating a direct connection.
• chore: bump zxing-cpp, switch to pnpm and renovate #127: Updates the zxing-cpp dependency, related to the main PR's changes.
• Version Packages #130: Addresses a bump in the zxing-cpp dependency, aligning with the updates made in the main PR.
• Version Packages #153: Includes a version update for zxing-cpp, related to the main PR's changes.
• Version Packages #160: Documents a bump of the zxing-cpp dependency, consistent with the changes made in the main PR.
• Version Packages #164: Features a patch change that bumps the zxing-cpp dependency, directly relating to the updates in the main PR.

🐇 In the code we hop and play,
Bumping versions on our way.
PDF417, now in line,
With each change, our code will shine!
Changelog updated, all is bright,
Hooray for fixes, what a sight!
🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1a9a372 and a87b193.

📒 Files selected for processing (3)

• .changeset/curly-houses-bathe.md (0 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

💤 Files with no reviewable changes (1)

• .changeset/curly-houses-bathe.md

✅ Files skipped from review due to trivial changes (1)

• package.json

🔇 Additional comments (1)

CHANGELOG.md (1)

3-7: LGTM! Version entry is well-documented and consistent.

The new version entry follows the established format and accurately documents the patch change. The version bump to 1.3.4 is appropriate for a bug fix, and the changelog entry properly references both the dependency update and its purpose.

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/zxing-wasm@172

commit: a87b193