Skip to content

chore(deps): bump the minor-and-patch group across 1 directory with 9 updates #34

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump the minor-and-patch group across 1 directory with 9 updates #34

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
18 changes: 9 additions & 9 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,26 +26,26 @@
"@react-three/fiber": "^9.6.1",
"@vercel/analytics": "^2.0.1",
"clsx": "^2.1.1",
"hamo": "1.0.0-dev.13",
"next": "16.2.9",
"hamo": "1.0.1",

@darkestdarky-bot darkestdarky-bot Bot Sep 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

hamo moves from a dev prerelease (1.0.0-dev.13) to stable 1.0.1. Verify the stable release does not change hook APIs used in this repo; a prerelease-to-stable jump can include breaking changes not captured by semver.

"next": "16.2.12",
"postprocessing": "^6.39.1",
"react": "19.2.7",
"react": "19.2.8",
"react-colorful": "^5.6.1",
"react-dom": "19.2.7",
"react-dom": "19.2.8",
"tempus": "1.0.0-dev.17",
"three": "0.184.0",
"three": "0.185.1",

@darkestdarky-bot darkestdarky-bot Bot Sep 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

three is still 0.x, so a minor bump (0.184.0 -> 0.185.1) can include breaking API changes. The standards require checking breaking changes before dependency upgrades; verify the three release notes and run bunx tsc --noEmit and the build before merge.

"zod": "^4.4.3",
"zustand": "^5.0.14"
},
"devDependencies": {
"@biomejs/biome": "2.5.1",
"@next/bundle-analyzer": "16.2.9",
"@biomejs/biome": "2.5.6",
"@next/bundle-analyzer": "16.2.12",
"@svgr/webpack": "^8.1.0",
"@tailwindcss/postcss": "^4.3.0",
"@types/node": "^24.0.0",
"@types/react": "19.2.17",
"@types/react": "19.2.18",
"@types/react-dom": "^19.2.3",
"@types/three": "^0.184.0",
"@types/three": "^0.185.1",

@darkestdarky-bot darkestdarky-bot Bot Sep 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@types/three uses a caret range (^0.185.1) while three is pinned exact (0.185.1). In 0.x, caret allows patch drift within 0.185.x, which can desynchronize type definitions from the runtime. Consider pinning @types/three to the exact matching version or ensure the lockfile resolves a compatible pair.

"babel-plugin-react-compiler": "^1.0.0",
"lefthook": "^2.1.9",
"tailwindcss": "^4.3.0",
Expand Down
Loading