mirror of
https://github.com/oxc-project/oxc.git
synced 2026-09-14 19:36:11 +08:00
codex/parser-grouped-expression-allocation
4 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 renovate[bot]
|
9688d38dfa |
chore(deps): update github actions (#26364)
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [benc-uk/workflow-dispatch](https://redirect.github.com/benc-uk/workflow-dispatch) | action | patch | `v1.3.2` → `v1.3.3` | | | [mlugg/setup-zig](https://redirect.github.com/mlugg/setup-zig) | action | minor | `v2` → `v2.2.1` | | | [semgrep/semgrep](https://redirect.github.com/semgrep/semgrep-proprietary) | container | minor | `1.175.0` → `1.176.0` | `1.176.1` | | [taiki-e/install-action](https://redirect.github.com/taiki-e/install-action) | action | patch | `v2.87.0` → `v2.87.4` | `v2.87.6` (+1) | --- ### Release Notes <details> <summary>benc-uk/workflow-dispatch (benc-uk/workflow-dispatch)</summary> ### [`v1.3.3`](https://redirect.github.com/benc-uk/workflow-dispatch/releases/tag/v1.3.3) [Compare Source](https://redirect.github.com/benc-uk/workflow-dispatch/compare/v1.3.2...v1.3.3) ##### What's changed since v1.3.2 ##### Fixed - Continue polling while a dispatched workflow run is in the `pending` state, preventing premature completion warnings and a `null` conclusion for workflows using concurrency groups or waiting for a runner. ([#​97](https://redirect.github.com/benc-uk/workflow-dispatch/issues/97), fixes [#​106](https://redirect.github.com/benc-uk/workflow-dispatch/issues/106)) ##### Notes - No breaking changes. - The floating `v1` and `v1.3` tags have been moved to point at `v1.3.3`. **Full changelog**: <https://github.com/benc-uk/workflow-dispatch/compare/v1.3.2...v1.3.3> </details> <details> <summary>mlugg/setup-zig (mlugg/setup-zig)</summary> ### [`v2.2.1`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.2.1) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.2.0...v2.2.1) - Print which version of Zig was installed - Add a little more log output (helps debug cache issues) > \[!NOTE] > The setup-zig project is now hosted on [Codeberg](https://codeberg.org/mlugg/setup-zig), and this GitHub repository exists as a mirror solely to work around the vendor lock-in mechanisms employed by GitHub Actions. While there are **no plans** to discontinue GitHub Actions support, I would nonetheless encourage users to consider upgrading to Forgejo Actions on a non-profit forge like Codeberg to avoid being affected by GitHub's profit-driven behavior (such as attempting to [charge users by the minute for using their own hardware](https://resources.github.com/actions/2026-pricing-changes-for-github-actions/)). ### [`v2.2.0`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.2.0) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.1.0...v2.2.0) - Update dependencies - Replace libsodium dependency with node:crypto, improving target support - Use hardcoded mirror list when ziglang.org is inaccessible - Fix incorrect tarball names when fetching certain versions > \[!NOTE] > The setup-zig project is now hosted on [Codeberg](https://codeberg.org/mlugg/setup-zig), and this GitHub repository exists as a mirror solely to work around the vendor lock-in mechanisms employed by GitHub Actions. While there are **no plans** to discontinue GitHub Actions support, I would nonetheless encourage users to consider upgrading to Forgejo Actions on a non-profit forge like Codeberg to avoid being affected by GitHub's profit-driven behavior (such as attempting to [charge users by the minute for using their own hardware](https://resources.github.com/actions/2026-pricing-changes-for-github-actions/)). ### [`v2.1.0`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.1.0) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.0.5...v2.1.0) - Support Forgejo Actions - Support recent Zig versions on ARM - Progress towards better OS support - Redirect Zig caches to working directory to avoid sharing the cache on self-hosted runners ### [`v2.0.5`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.0.5) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.0.4...v2.0.5) - Fix exception identifying Zig cache directory on recent Zig builds ([#​49](https://redirect.github.com/mlugg/setup-zig/issues/49)) ### [`v2.0.4`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.0.4) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.0.3...v2.0.4) - Fix canonical `ziglang.org` download URL - Use more descriptive `?source` query parameter value ### [`v2.0.3`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.0.3) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.0.2...v2.0.3) This release switches from a hardcoded `mirrors.json` list, to fetching the list of mirrors [now available](https://ziglang.org/download/community-mirrors/) from the Zig website. There are no user-facing changes. ### [`v2.0.2`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.0.2) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2.0.1...v2.0.2) - Update dependencies - Remove some mirrors experiencing issues - Don't use tool cache on GitHub-hosted runners by default ([#​34](https://redirect.github.com/mlugg/setup-zig/issues/34)) - Improve logging, in particular to help debug potential issues ### [`v2.0.1`](https://redirect.github.com/mlugg/setup-zig/releases/tag/v2.0.1) [Compare Source](https://redirect.github.com/mlugg/setup-zig/compare/v2...v2.0.1) The recent Zig 0.14.1 release flipped the "arch" and "OS" fields in the tarball name; for instance, `zig-x86_64-linux-0.14.1.tar.xz` instead of `zig-linux-x86_64-0.14.1.tar.xz`. This brings the tarball names in line with target triple syntax. The change does *not* retroactively apply to old Zig tarballs. So, this patch has only one fix: - Add support for new Zig tarball name format as of Zig 0.14.1 / 0.15.0-dev.631+9a3540d61 > \[!NOTE] > > **I do not intend to update v1 to support the new tarball name format.** > `setup-zig` version 1 is considered deprecated. Please upgrade to version 2. </details> <details> <summary>taiki-e/install-action (taiki-e/install-action)</summary> ### [`v2.87.4`](https://redirect.github.com/taiki-e/install-action/releases/tag/v2.87.4): 2.87.4 [Compare Source](https://redirect.github.com/taiki-e/install-action/compare/v2.87.3...v2.87.4) - Update `uv@latest` to 0.12.8. - Update `protoc@latest` to 3.36.1. - Update `coreutils@latest` to 0.11.0. ### [`v2.87.3`](https://redirect.github.com/taiki-e/install-action/releases/tag/v2.87.3): 2.87.3 [Compare Source](https://redirect.github.com/taiki-e/install-action/compare/v2.87.2...v2.87.3) - Update `zizmor@latest` to 1.30.0. - Update `ubi@latest` to 0.12.0. - Update `protoc-gen-connect-openapi@latest` to 0.25.8. - Update `mise@latest` to 2026.8.16. - Update `kingfisher@latest` to 2.1.0. - Update `dprint@latest` to 0.57.0. ### [`v2.87.2`](https://redirect.github.com/taiki-e/install-action/releases/tag/v2.87.2): 2.87.2 [Compare Source](https://redirect.github.com/taiki-e/install-action/compare/v2.87.1...v2.87.2) - Update `typos@latest` to 1.50.0. - Update `tombi@latest` to 1.5.0. - Update `shfmt@latest` to 3.14.0. ### [`v2.87.1`](https://redirect.github.com/taiki-e/install-action/releases/tag/v2.87.1): 2.87.1 [Compare Source](https://redirect.github.com/taiki-e/install-action/compare/v2.87.0...v2.87.1) - Update `uv@latest` to 0.12.7. - Update `typos@latest` to 1.49.1. - Update `syft@latest` to 1.51.1. - Update `prek@latest` to 0.5.0. - Update `d2@latest` to 0.8.2. - Update `cargo-zigbuild@latest` to 0.23.3. - Update `cargo-rdme@latest` to 2.2.2. - Update `biome@latest` to 2.5.11. </details> --- ### Configuration 📅 **Schedule**: (in timezone Asia/Shanghai) - Branch creation - "before 10am on monday" - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/oxc-project/oxc). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC42MS4zIiwidXBkYXRlZEluVmVyIjoiNDQuNjEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|
Dunqing
|
e8caf5bb74 |
fix(ci): allow Monitor Oxc on fork pull requests (#25055)
The [Monitor Oxc job](https://github.com/oxc-project/oxc/actions/runs/30413998931/job/90456346227?pr=25041) fails for fork PRs because `pull_request` workflows do not receive repository secrets, leaving the GitHub App client ID empty. Keep the `run-monitor-oxc` label trigger for same-repository PRs. Fork label events are skipped before secrets are used; a trusted maintainer can trigger them with `/monitor-oxc run` instead. The comment path verifies triage permission, rejects PRs pushed after the command, and dispatches the exact head SHA. This follows [Vite's ecosystem CI workflow](https://github.com/vitejs/vite/blob/main/.github/workflows/ecosystem-ci-trigger.yml). Verified with `just ready`. AI assistance was used to investigate the failure and prepare this change. |
||
|
camc314
|
6d1b642e47 |
feat(ci): remove run-monitor-oxc trigger label after workflow dispatch (#22879)
|
||
|
Dunqing
|
d5d0cf345a |
ci(monitor-oxc): trigger via run-monitor-oxc PR label (#22712)
## Summary Add `.github/workflows/monitor-oxc.yml`. When a maintainer adds the `run-monitor-oxc` label to a PR, the workflow posts a placeholder comment, mints a GitHub App token, and dispatches `ci.yml` on `oxc-project/monitor-oxc` with `issue-number`, `comment-id`, and `ref: refs/pull/N/head`. monitor-oxc's existing `comment` job then edits the placeholder in place with the per-suite result table. Consolidates the duplicated dispatch logic in `prepare_release_crates.yml`: the standalone `ecosystem-ci` job (and the now-unused `outputs:` on `prepare`) is replaced by a single `labels: run-monitor-oxc` input on `peter-evans/create-pull-request`. Because the action creates the PR with the App token, attaching the label fires `pull_request: labeled` on `oxc-project/oxc` and re-enters the new workflow. ## Operational notes - The `run-monitor-oxc` label needs to be created once in repo settings — proposed color `#55e1cc` (same as `run-bench`) with description "Add to a PR to dispatch oxc-project/monitor-oxc CI against it". The workflow's `if:` guard ignores the event when the label name doesn't match, so missing the label only means the workflow does nothing — no errors. - The GitHub App is already authorized to dispatch into `monitor-oxc` (same `repositories: monitor-oxc` token mint used by the old `ecosystem-ci` job in `prepare_release_crates.yml`). - One-shot: removing and re-adding the label dispatches a new run. Pushing new commits while the label is still attached does **not** auto-retrigger. ## Behavior delta for release-prep flow - *Before:* dispatch passed no `ref`, so monitor-oxc defaulted to `main` and tested `oxc-project/oxc@main` as of dispatch time (pre version-bump). - *After:* dispatch passes `refs/pull/N/head`, so monitor-oxc tests the release PR branch (main + version-bump commit). Version-bump commits only touch `Cargo.toml` / `package.json` versions — no transformer/codegen/etc. code paths. So monitor-oxc's results are functionally identical; arguably slightly better since it tests the exact code that ships. |