build: Update swc_core to v69.0.0

[Donny/강동윤 (kdy1)]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 068825d

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@​68.0.2 ⏵ 69.0.0
	cargo/​swc_ecma_transforms_base@​44.0.0 ⏵ 44.0.2
	cargo/​swc_ecma_minifier@​55.0.0 ⏵ 55.0.2
	cargo/​swc_ecma_codegen@​28.0.0 ⏵ 28.0.1
	cargo/​swc_ecma_parser@​41.0.0 ⏵ 41.1.0
	cargo/​swc_ecma_transforms@​55.0.0 ⏵ 55.0.1
	cargo/​swc_common@​23.0.0 ⏵ 23.0.1

View full report

[claude]

PR Review: build: Update swc_core to v69.0.0

Reviewed the full diff (83 files, +276/-75). This is an automated release PR that bumps the swc_core dependency, consumes a pending changeset, and rolls package/crate versions + generated changelogs. Summary of what's actually here:

• Dependency bumps in root Cargo.toml: swc_core 68.0.2 → 69.0.0 (major), plus aligned bumps to swc_common, swc_ecma_*, and the local swc_icu_messageformat_parser (27 → 28).
• Version bumps across 18 packages/crates + regenerated CHANGELOG.md/README.md and Cargo.lock.
• Changeset consumed: .changeset/ten-heads-beg.md (emotion: "Fix extraneous spaces in compiled template strings").
• No .rs source changes anywhere in the diff.

Assessment

✅ Low risk. The headline is a major swc_core bump (68 → 69), yet zero source edits were required to compile against it — a good signal that the upgrade is API-compatible for this repo. Lockfile checksums and versions are consistent with the manifest changes.

✅ Mechanics look correct. Version rolls are internally consistent (all published packages land on the synchronized *.13.0 line), and the changelog/README regeneration matches the consumed changeset.

Things worth a quick look

1. Changeset bump level vs. applied bump. ten-heads-beg.md declares emotion as a patch, but @swc/plugin-emotion went 14.12.0 → 14.13.0 (a minor), and the underlying swc_emotion transform crate went 8.0.0 → 9.0.0 (a major). This appears to be the repo's intentional version-synchronization policy rather than a bug, but it's worth confirming the major crate bump is deliberate — consumers pinning swc_emotion will need to update.

2. CI is the real gate. Since there are no source changes, correctness rests entirely on the existing test suites passing against swc_core v69. Please make sure the full plugin test matrix (and ideally a .wasm build smoke test) is green before merging — a major core bump can change AST/transform behavior even when the Rust API surface is unchanged.

Security / performance

No concerns. No source or build-script changes; only registry-pinned dependency upgrades with verified checksums in Cargo.lock.

Verdict: Looks good to merge once CI is green. The only follow-up I'd suggest is double-checking the intended semver level for the emotion crate's major bump. 👍

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 068825dff9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

[chatgpt-codex-connector]

Update Cargo.lock for the bumped local crates

When this path crate version is bumped, the committed Cargo.lock also needs to be regenerated; it still records swc_emotion as 8.0.0 (and similarly leaves the other local crates at their pre-bump versions). Locked Cargo builds or release jobs that rely on the committed lockfile will refuse to rewrite it, while unlocked builds will dirty the checkout by updating the lockfile during the build.

Useful? React with 👍 / 👎.