Skip to content

Track oxc changes up to the latest release tags - #48

Merged
bachmacintosh merged 1 commit into
mainfrom
claude/dazzling-keller-6hxt2u
Oct 17, 2026
Merged

bachmacintosh merged 1 commit into
mainfrom
claude/dazzling-keller-6hxt2u

Conversation

@bachmacintosh

Copy link
Copy Markdown
Contributor

Summary

  • Renovate: removes the packageRules entry that updated oxfmt, oxlint and oxlint-tsgolint as soon as releases passed minimumReleaseAge. They now follow the shared preset's normal schedule.
  • scripts/oxc-version-diff.ts: the upper bound is now the newest oxlint_v* / oxfmt_v* tag in oxc-project/oxc (from git ls-remote) that's also published on npm, not our devDependency. The script installs both the peer-floor and the latest versions into a temp directory and diffs the catalog and schemas between them. The report adds a "Latest release" column and a "Releases in range" section that links each release to its GitHub release. It uses the apps_v* tag when oxlint and oxfmt shipped from the same commit, and marks releases that aren't in devDependencies yet. If a tag isn't on npm yet, that release is left out and the report notes it. If the tags can't be listed, the script falls back to npm's latest dist-tag and notes that too.
  • oxc-peer-tracker skill: describes the new range and when to refresh. It also adds a CI preview step: when the latest release is newer than devDependencies, it runs the pr.yml CI steps against the latest versions in a throwaway git worktree and records any failure in the issue.
  • Issue template: new title ("…between peerDependencies and the latest releases"), a "Latest release" column, a "(not in devDependencies yet)" marker, a "CI preview with the latest releases" line, and a note that the peer floor can only go up to what devDependencies (and so CI) run. The skill finds the issue by its marker and renames it from the old title on the next refresh.

Testing

  • pnpm typecheck, pnpm lint, pnpm format:check and pnpm test all pass.
  • Ran the script with the current versions: the range is empty because peer = dev = latest (oxlint 1.88.0, oxfmt 0.73.0).
  • Temporarily lowered the peer ranges to ^1.83.0 / >=0.68.0 <1: the script listed releases 1.84.0–1.88.0 and 0.69.0–0.73.0 with the right tags (apps_v1.84.0 for both tools' combined release) and gave the expected catalog and schema diffs.
  • Forced git ls-remote to fail: the script fell back to npm's latest dist-tag and noted it in the report.
  • Tested the CI-preview worktree commands by pinning oxlint to 1.87.0. They caught the real typecheck/lint failure on unicorn/prefer-query-selector options, and the main checkout stayed untouched.

Generated by Claude Code

The oxc-peer-tracker skill now compares the peerDependencies floor against
the newest oxlint/oxfmt releases tagged in oxc-project/oxc instead of our
devDependencies, so the tracking issue covers releases before Renovate
brings them in. scripts/oxc-version-diff.ts lists the tags with
`git ls-remote`, takes the newest one published on npm as the upper bound
and links each release in range. The skill also runs the PR CI steps
against the latest releases in a throwaway worktree to flag failures early.

With that in place, drop the Renovate rule that updated oxc tooling as
soon as releases passed minimumReleaseAge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Em5Kt9FdzYzHk2YX2vmo7N
@bachmacintosh
bachmacintosh marked this pull request as ready for review October 17, 2026 05:56
@bachmacintosh
bachmacintosh added this pull request to the merge queue Oct 17, 2026
Merged via the queue into main with commit 593ff9e Oct 17, 2026
2 checks passed
@bachmacintosh
bachmacintosh deleted the claude/dazzling-keller-6hxt2u branch October 17, 2026 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants