Skip to content

build: Update swc_core to v59.0.1#601

Merged
kdy1 merged 1 commit into
mainfrom
kdy1/bump
Mar 22, 2026
Merged

build: Update swc_core to v59.0.1#601
kdy1 merged 1 commit into
mainfrom
kdy1/bump

Conversation

@kdy1
Copy link
Copy Markdown
Member

@kdy1 kdy1 commented Mar 22, 2026

No description provided.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Mar 22, 2026

⚠️ No Changeset found

Latest commit: 4f2c3be

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

@kdy1 kdy1 enabled auto-merge (squash) March 22, 2026 06:58
@claude
Copy link
Copy Markdown

claude Bot commented Mar 22, 2026

PR Review: build: Update swc_core to v59.0.1

This is a routine dependency update PR. Here's my assessment:

Summary of Changes

  • swc_core: 58.0.159.0.1
  • swc_ecma_minifier: 46.0.047.0.0
  • swc_ecma_parser: 35.0.036.0.0
  • swc_ecma_transforms: 48.0.049.0.0
  • swc_ecma_transforms_base: 38.0.039.0.0
  • swc_ecma_transforms_react: 42.0.043.0.0
  • swc_ecma_transforms_testing: 42.0.043.0.0
  • swc_sourcemap: 9.3.010.0.2

Observations

Positive:

  • The Cargo.lock cleanup consolidates two previously coexisting versions of swc_sourcemap (9.3.4 and 10.0.2) down to a single version (10.0.2). This reduces dependency duplication and likely shrinks binary size slightly.
  • Version bumps are consistent and coherent across the SWC ecosystem — no mismatched transitive dependencies visible in the lock file.
  • All checksums are updated correctly in Cargo.lock.
  • No source code changes, reducing risk.

No concerns:

  • These are all internal SWC ecosystem crates maintained by the same team, so breaking-change risk is managed upstream.
  • Security check (Socket Security) passed.
  • Auto-merge is appropriately enabled for this type of maintenance PR.

Verdict

LGTM. Clean, minimal dependency update with a nice side effect of deduplicating the swc_sourcemap dependency. Pending CI results should confirm compatibility.

@kdy1 kdy1 merged commit db497f0 into main Mar 22, 2026
11 checks passed
@kdy1 kdy1 deleted the kdy1/bump branch March 22, 2026 07:03
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4f2c3bef6f

ℹ️ 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 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 address that feedback".

Comment thread Cargo.toml
swc_cached = "2.0.0"
swc_common = "19.0.0"
swc_core = "58.0.1"
swc_core = "59.0.1"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Bump npm package versions for the new swc_core ABI

This updates the Rust workspace to swc_core 59.0.1, but none of the published plugin packages were versioned for that new compatibility line: for example packages/remove-console/package.json:3 is still 12.7.0, and its changelog still says 12.7.0 is the v58.0.1 release (packages/remove-console/CHANGELOG.md:3-7). The repo itself tells users to select plugin versions by swc_core compatibility (contrib/mut-cjs-exports/README.md:11-13), so leaving the npm versions unchanged means the next publish cannot ship a distinct v59-compatible release and risks host/plugin version-mismatch failures for consumers still pinned to the current v58-compatible packages.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant