chore(deps): converge oxfmt on ^0.61.0 (WR-0495) - #199
Merged
Conversation
Part of the fleet oxfmt convergence. The fleet had split three ways (^0.59 / ^0.60 / ^0.61); `^0.x` locks the minor in npm semver, so the ranges must move explicitly. Verified output-identical before bumping: `oxfmt@0.59.0 --check` and `oxfmt@0.61.0 --check` flag the same file set on this repo's own format target. format:check verified after bump. Diff is manifest + lockfile only. Partially supersedes dependabot #189 (oxfmt leg only; its oxlint 1.74 -> 1.76 leg is unaffected and remains open). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012QpHumQkpoipXd6oMuy1aB
Goosterhof
added
the
Agent Review Requested
Goosterhof
added
the
Agent Review Requested
dmooibroek
approved these changes
Jul 29, 2026
There was a problem hiding this comment.
Clean. Verified the containment claim independently: root package.json moves only oxfmt ^0.59.0 -> ^0.61.0 in devDependencies, and the lockfile diff touches zero non-oxfmt node_modules/ entries. Checked the publish angle for this repo specifically — no published sub-package declares oxfmt in dependencies or peerDependencies, so the range change is not consumer-visible on the npm registry.
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
2 participants
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.
What
Converges
oxfmton^0.61.0as part of the fleet-wide alignment tracked by WR-0495.The fleet had drifted into a three-way split —
^0.59/^0.60/^0.61across ten repos. Because^0.xlocks the minor in npm semver,^0.59.0genuinely refuses0.60.0; the ranges have to be moved explicitly, which is why dependabot had an open oxfmt PR on most of these repos.Why this is safe — measured, not assumed
WR-0495 was originally written on the assumption that "an oxfmt minor can reflow files fleet-wide", which justified a cautious one-repo-at-a-time rollout. That assumption was tested and does not hold for this hop.
oxfmt@<old> --checkvsoxfmt@0.61.0 --check, each run against this repo's ownformat:checktarget (not a guessed path):tint(...)call onto one line. Folded into that repo's own PR.Positive control (§ Null-Result Gate — a clean result is only meaningful if the instrument is known to fire): a deliberately misformatted file was introduced,
--checkcorrectly flagged it, and the file was restored. The check is not silently passing.The diff
Manifest + lockfile only. Every added lockfile entry was verified to be an
oxfmtpackage — no unrelated dependency moved.Verification
format:check— run after the bump, result recorded in the commit message🤖 Generated with Claude Code
https://claude.ai/code/session_012QpHumQkpoipXd6oMuy1aB