build: Update swc_core to v71.0.5

[kdy1]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2387df9

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​swc_core@​71.0.0 ⏵ 71.0.5
	cargo/​swc_ecma_transforms_base@​44.0.3 ⏵ 44.0.4
	cargo/​swc_ecma_minifier@​56.0.1 ⏵ 56.0.2	+1
	cargo/​swc_ecma_parser@​41.1.1 ⏵ 41.1.2
	cargo/​swc_ecma_utils@​31.0.1 ⏵ 31.0.2
	cargo/​swc_plugin_macro@​1.1.0 ⏵ 1.1.1			+4

View full report

[claude]

PR Review — build: Update swc_core to v71.0.5

Reviewed the full diff. This is an automated changeset release PR (a swc_core bump folded together with the release of 18 packages). Nothing here is hand-written logic, so the review is mostly a consistency/hygiene check.

✅ What looks good

• Dependency bump is coherent. swc_core 71.0.0 → 71.0.5 in Cargo.toml matches Cargo.lock (checksum updated), and the transitive swc_ecma_* crates are pulled forward consistently (swc_ecma_minifier 56.0.1→56.0.2, swc_ecma_parser 41.1.1→41.1.2, swc_ecma_transforms_base 44.0.3→44.0.4, swc_ecma_transforms_optimization 47.0.1→47.0.2, swc_ecma_utils 31.0.1→31.0.2, swc_plugin_macro 1.1.0→1.1.1).
• Version bookkeeping is internally consistent. The 3 consumed changesets (fix-emotion-dynamic-css-arrays, formatjs-throws-false, quiet-emotion-spans) are deleted and their entries land in both the CHANGELOG.md and README.md for the affected packages. package.json npm versions and the internal Rust crate versions line up — e.g. swc_formatjs_transform 33→34 and the matching swc_icu_messageformat_parser 29.0.0→30.0.0 reference are updated in lockstep in packages/formatjs/transform/Cargo.toml.

🔎 Worth a second look (non-blocking)

1. Semver of the folded-in changes. packages/formatjs ships "Add throws: false support to skip non-static FormatJS descriptors" as a patch (9.14.0 → 9.14.1). Adding a new config option is usually a minor under semver — patch releases that introduce behavior/options can surprise consumers who pin on ~. Same category for the two emotion behavioral changes. This originates in the original feature PRs' changeset metadata rather than this release PR, but it's the last chance to correct the bump level before publish.
2. Behavior-affecting core bump — lean on CI. A swc_core update can subtly shift transform output. Since this PR touches no fixtures/tests, please confirm the build + snapshot/plugin-behavior test suites are green before merge; that's the real safety net here.
3. Internal transform crates get major bumps (most 10.0.0 → 11.0.0, plus swc_mut_cjs_exports 21→22) while the npm plugins are patch-only. That's expected if the swc_core API change forced a breaking bump on the transform crates — just calling it out so it's an intentional choice, not a surprise for anyone consuming those crates directly from crates.io.

Security / performance

No concerns — this is dependency version metadata and generated changelog text only. No new attack surface, no runtime changes in this repo's own code.

Overall: LGTM as a routine release, pending green CI. The only judgment call is the patch-vs-minor question in (1).