Skip to content

chore(deps): update dependency oxfmt to v0.50.0 #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
renovate merged 1 commit into from
May 20, 2026
+81 −81
Merged

chore(deps): update dependency oxfmt to v0.50.0 #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
160 changes: 80 additions & 80 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@
"marked": "18.0.3",
"marked-terminal-renderer": "2.2.0",
"open": "11.0.0",
"oxfmt": "0.49.0",
"oxfmt": "0.50.0",
Copy link
Copy Markdown
Member

@doistbot doistbot May 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Bumping oxfmt to 0.50.0 raises its declared Node engine to ^20.19.0 || >=22.12.0 (see the updated lockfile), which is stricter than this repo’s documented/package floor of >=20.18.1. That means engine-strict installs on the currently advertised minimum Node version will start failing. Either keep oxfmt on 0.49.0, or update this repo’s Node baseline (package.json, README, etc.) in the same PR if the support floor is intentionally changing.

"oxlint": "1.64.0",
"semantic-release": "25.0.3",
"typescript": "6.0.3",
Expand Down
Loading