feat: bug version @swc/core 1.13.21

[shiftj18]

Summary by CodeRabbit

• Chores
  • Updated dependency configuration to address a known issue with a build tool.

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

A new bug-version mapping was added to package.json under the @swc/core dependency, documenting a known compatibility issue between versions 1.13.21 and 1.3.20 with a reference to the corresponding GitHub issue for tracking.

Changes

Cohort / File(s)	Summary
Bug-version mapping update package.json	Added new @swc/core bug-version entry: "1.13.21" → "1.3.20" with GitHub issue reference

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• fengmk2

Poem

🐰 A mapping new, a bug we track,
From 1.13.21, we know the stack,
To 1.3.20, the path is clear,
GitHub's wisdom we hold dear! 🎯

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "feat: bug version @swc/core 1.13.21" is directly related to the main change in the changeset, which adds a new bug-version mapping for @swc/core version 1.13.21. The title is specific and concise, clearly identifying the package name and version being added, which allows a teammate scanning the history to quickly understand that this pull request introduces a bug-version entry for @swc/core 1.13.21. The title accurately summarizes the primary change without vague language or unnecessary noise.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @shiftj18, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a specific bug identified in @swc/core version 1.13.21. To mitigate this issue, a version override has been implemented within the package.json file. This change ensures that any dependency requesting 1.13.21 will instead resolve to the more stable 1.3.20, effectively bypassing the problematic version as detailed in the linked SWC issue.

Highlights

• @swc/core Version Override: Introduced a version override for @swc/core version 1.13.21 in package.json, directing it to use 1.3.20 to resolve a known bug, referencing issue #11176.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request adds a new entry to the bug-versions configuration in package.json for @swc/core version 1.13.21, indicating that it should be downgraded to version 1.3.20 due to issue https://github.com/swc-project/swc/issues/11176. This change aims to address a bug in the specified version of the @swc/core package.

[Copilot]

Pull Request Overview

This PR addresses a bug in @swc/core version 1.13.21 by adding a version override configuration that downgrades it to version 1.3.20.

Key Changes

• Added a new version resolution override for @swc/core 1.13.21, pinning it to 1.3.20 due to a documented issue

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

🎉 This PR is included in version 1.118.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀