swc-project/swc - CodSpeed

swc

Blog Docs Changelog

Performance History

Latest Results

ci: allow memmap2 advisory (#11961) **Description:** Allow `RUSTSEC-2026-0186` in `deny.toml` so `cargo deny check` passes after the new RustSec advisory for `memmap2 0.6.2`. `memmap2` is constrained by `shared-buffer 0.1.4`, which is pulled in through Wasmer. There is no newer crates.io release of `shared-buffer`, and local source inspection shows it only uses `Mmap::map`, not the affected range advice/flush APIs described by the advisory. Validation: - `git submodule update --init --recursive` - `cargo deny check` - `cargo fmt --all` - `cargo clippy --all --all-targets -- -D warnings` **BREAKING CHANGE:** None. **Related issue (if exists):** CI job: https://github.com/swc-project/swc/actions/runs/28000731021/job/82872355038

main

53 minutes ago

chore: allow memmap2 advisory

kdy1/ignore-memmap2-advisory

1 hour ago

ci: allow publish milestone PR updates (#11960) **Description:** Fixes the publish workflow milestone manager permissions. The `manage-milestone` job updates milestones on merged pull requests through GitHub's issues API, but the job only had `pull-requests: read`, which caused GitHub to reject PR milestone updates with `HTTP 403 Resource not accessible by integration`. This keeps the permission change scoped to the `manage-milestone` job and changes `pull-requests` from `read` to `write` so release milestone automation can update PR milestones. Validation: - `git diff --check -- .github/workflows/publish.yml` - YAML parse check for `.github/workflows/publish.yml` **Related issue:** Related failing workflow job: https://github.com/swc-project/swc/actions/runs/27955860105/job/82869289735

main

5 hours ago

ci: allow publish milestone PR updates

codex/fix-publish-milestone-permission

6 hours ago

chore: add changeset for async generator env fix

codex/fix-async-generator-chrome-60

22 hours ago

fix(preset-env): downlevel async generators for chrome 60

codex/fix-async-generator-chrome-60

23 hours ago

fix(react-compiler): disable parser default features (#11957) **Description:** Disable `swc_ecma_parser` default features in `swc_ecma_react_compiler` and explicitly keep the `typescript` feature enabled. This fixes the s390x publish failure where parser defaults enabled `stacker -> psm`, and `psm` failed to assemble its s390x stack-switching source under the `napi-cross` toolchain. TypeScript parsing support remains enabled for react-compiler code and tests. Validated with: - `git submodule update --init --recursive` - `cargo tree -p binding_react_compiler_node -e features --target s390x-unknown-linux-gnu -i psm` (confirms `psm` is absent) - `cargo tree -p binding_core_node -e features --no-default-features --features swc_v1 --target s390x-unknown-linux-gnu -i psm` (confirms `psm` is absent) - `cargo test -p swc_ecma_react_compiler` - `cargo fmt --all` - `cargo clippy --all --all-targets -- -D warnings`

main

1 day ago

chore: add changeset for react compiler parser defaults

codex/fix-s390x-parser-defaults

1 day ago

Latest Branches

+2%

ci: allow memmap2 advisory#11961

1 hour ago

57d0037

kdy1/ignore-memmap2-advisory

-2%

ci: allow publish milestone PR updates#11960

6 hours ago

c771092

codex/fix-publish-milestone-permission

0%

fix(es/preset-env): fix async generator env transform for Chrome 60#11959

23 hours ago

41fd10c

codex/fix-async-generator-chrome-60

© 2026 CodSpeed Technology

Home Terms Privacy Docs