build(deps-dev): bump the development-minor-and-patch group with 2 updates - #161
Conversation
…dates Bumps the development-minor-and-patch group with 2 updates: [oxfmt](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxfmt) and [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint). Updates `oxfmt` from 0.58.0 to 0.59.0 - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxfmt/CHANGELOG.md) - [Commits](https://github.com/oxc-project/oxc/commits/oxfmt_v0.59.0/npm/oxfmt) Updates `oxlint` from 1.73.0 to 1.74.0 - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md) - [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.74.0/npm/oxlint) --- updated-dependencies: - dependency-name: oxfmt dependency-version: 0.59.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-minor-and-patch - dependency-name: oxlint dependency-version: 1.74.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Codex review: needs maintainer review before merge. Reviewed July 20, 2026, 12:10 PM ET / 16:10 UTC. Summary Reproducibility: not applicable. This PR updates development tooling rather than fixing a reported runtime behavior. The supplied CI provides the relevant automated validation for the proposed versions. Review metrics: 2 noteworthy metrics.
Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Next step before merge
Security Review detailsBest possible solution: Merge the focused, lockfile-consistent development-tool update after ordinary maintainer review; retain the current repository formatter and linter configuration unless an observed post-update incompatibility requires a separate change. Do we have a high-confidence way to reproduce the issue? Not applicable: this PR updates development tooling rather than fixing a reported runtime behavior. The supplied CI provides the relevant automated validation for the proposed versions. Is this the best way to solve the issue? Yes. Updating the direct manifest entries together with the pnpm lockfile is the narrow, repository-consistent way to adopt these two development-tool releases. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 041bf4bfd670. Label changesLabel justifications:
Evidence reviewedWhat I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
|
Landed on Tested on exact Dependabot head
Registry freshness at merge: both target versions are the current npm |
Bumps the development-minor-and-patch group with 2 updates: oxfmt and oxlint.
Updates
oxfmtfrom 0.58.0 to 0.59.0Changelog
Sourced from oxfmt's changelog.
... (truncated)
Commits
2d4e8d2release(apps): oxlint v1.74.0 && oxfmt v0.59.0 (#24454)415fe1efix(oxfmt): error on ignorePatterns that cannot match files outside the confi...Updates
oxlintfrom 1.73.0 to 1.74.0Release notes
Sourced from oxlint's releases.
... (truncated)
Changelog
Sourced from oxlint's changelog.
Commits
2d4e8d2release(apps): oxlint v1.74.0 && oxfmt v0.59.0 (#24454)7f80cacperf(linter/vue/prop-name-casing): precompileignorePropsregex pattern (#2...6272051perf(linter/typescript/no-require-imports): compile allow patterns once (#24417)33805b9perf(linter/jsdoc/require-param): compile checkTypesPattern regex once (#24420)0433a83feat(linter/eslint/no-inner-declarations): addnamespacesoption (#24044)8337835fix(linter): error onignorePatternsthat cannot match files aoutside the c...2ce5a33fix(linter): resolveignorePatternsrelative to the config dir (#24339)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions