Repository navigation
Track oxc changes up to the latest release tags - #48
Merged
Merged
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
packageRulesentry that updatedoxfmt,oxlintandoxlint-tsgolintas soon as releases passedminimumReleaseAge. They now follow the shared preset's normal schedule.scripts/oxc-version-diff.ts: the upper bound is now the newestoxlint_v*/oxfmt_v*tag inoxc-project/oxc(fromgit 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 theapps_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'slatestdist-tag and notes that too.oxc-peer-trackerskill: 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 thepr.ymlCI steps against the latest versions in a throwawaygit worktreeand records any failure in the issue.Testing
pnpm typecheck,pnpm lint,pnpm format:checkandpnpm testall pass.^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.0for both tools' combined release) and gave the expected catalog and schema diffs.git ls-remoteto fail: the script fell back to npm'slatestdist-tag and noted it in the report.unicorn/prefer-query-selectoroptions, and the main checkout stayed untouched.Generated by Claude Code