chore(deps): pin dependencies - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@babel/core (source)	devDependencies	pin	^7.25.2 -> 7.25.2
@babel/types (source)	devDependencies	pin	^7.25.2 -> 7.25.2
@changesets/cli (source)	devDependencies	pin	^2.27.7 -> 2.27.7
@types/babel__core (source)	devDependencies	pin	^7.20.5 -> 7.20.5
@types/node (source)	devDependencies	pin	^22.4.2 -> 22.4.2
concurrently	devDependencies	pin	^8.2.2 -> 8.2.2
copy-files-from-to	devDependencies	pin	^3.11.0 -> 3.11.0
lint-staged	devDependencies	pin	^15.2.9 -> 15.2.9
npm-check-updates	devDependencies	pin	^17.0.6 -> 17.0.6
prettier (source)	devDependencies	pin	^3.3.3 -> 3.3.3
pretty-quick	devDependencies	pin	^4.0.0 -> 4.0.0
rimraf	devDependencies	pin	^6.0.1 -> 6.0.1
simple-git-hooks	devDependencies	pin	^2.11.1 -> 2.11.1
tsx (source)	devDependencies	pin	^4.17.0 -> 4.17.0
typedoc (source)	devDependencies	pin	^0.26.6 -> 0.26.6
typescript (source)	devDependencies	pin	^5.5.4 -> 5.5.4
vite (source)	devDependencies	pin	^5.4.2 -> 5.4.2
vite-plugin-babel	devDependencies	pin	^1.2.0 -> 1.2.0

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

---

Configuration

📅 Schedule: Branch creation - "before 9am on monday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9717b85

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Rate limit exceeded

@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 26 minutes and 15 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between d7edbdb and 9717b85.

Walkthrough

The changes encompass updates to GitHub Actions workflows and the package.json file. Specifically, action versions were modified from tagged releases to specific commit hashes, ensuring greater stability and predictability during workflow execution. Additionally, version specifications for development dependencies were adjusted to exact versions, eliminating the caret (^) to guarantee consistent builds. Together, these changes enhance the reliability of the project by locking dependencies and actions to known states.

Changes

Files	Change Summary
.github/actions/setup-emsdk/action.yml, .github/actions/setup-node/action.yml	Updated action versions from tagged releases (v4) to specific commit hashes, enhancing stability by ensuring known states of actions.
.github/workflows/deploy.yml, .github/workflows/preview-release.yml, .github/workflows/release.yml	Modified actions/checkout from version v4 to a specific commit hash, improving predictability and preventing potential breaking changes in future runs.
package.json	Changed development dependencies from caret versioning to exact versions, ensuring consistent builds and reducing the risk of issues due to unexpected minor updates.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Workflow
    participant Action1
    participant Action2

    User->>Workflow: Trigger workflow
    Workflow->>Action1: Use actions/setup-emsdk
    Workflow->>Action2: Use actions/setup-node
    Action1-->>Workflow: Complete setup
    Action2-->>Workflow: Complete setup
    Workflow->>Action1: Use actions/checkout
    Workflow->>Action2: Install Deno
    Action1-->>Workflow: Checkout code
    Action2-->>Workflow: Deno installed
    Workflow-->>User: Workflow complete

Loading

🐰 In a world of code and flow,
Where changes sprout and slowly grow,
Actions locked, both swift and neat,
Dependencies stand firm on their feet.
With every build, a happy cheer,
For stable paths, we hold so dear! 🐇✨

---

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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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]

commit: 9717b85

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

Open in Stackblitz

[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 4176035 and d7edbdb.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (6)

• .github/actions/setup-emsdk/action.yml (1 hunks)
• .github/actions/setup-node/action.yml (1 hunks)
• .github/workflows/deploy.yml (1 hunks)
• .github/workflows/preview-release.yml (1 hunks)
• .github/workflows/release.yml (1 hunks)
• package.json (1 hunks)

Files skipped from review due to trivial changes (4)

• .github/workflows/deploy.yml
• .github/workflows/preview-release.yml
• .github/workflows/release.yml
• package.json

Additional comments not posted (2)

.github/actions/setup-node/action.yml (1)

11-11: LGTM! Pinning action to a specific commit hash.

Pinning the actions/setup-node action to a specific commit hash ensures stability and predictability in workflow execution.

.github/actions/setup-emsdk/action.yml (1)

17-17: LGTM! Pinning action to a specific commit hash.

Pinning the actions/cache action to a specific commit hash ensures stability and predictability in workflow execution.