Skip to content

fix(deps): update dependencies #16

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
atldays merged 2 commits into from
Oct 13, 2026
Merged

fix(deps): update dependencies #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
755ce00
fix(deps): update dependencies
addon-stack-dependency-updates[bot] Oct 13, 2026
8918a5b
fix(deps): preserve release parser during lockfile updates
atldays Oct 13, 2026
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
7 changes: 7 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,13 @@ together with `package-lock.json`. Stable updates of any size share that PR, inc
The Chrome peer dependency remains `*`; unrelated direct dependencies and standalone lockfile maintenance are disabled.
Transitive lockfile changes required by the selected updates are still included.

Keep `conventional-commits-parser` 6.x as an explicit development dependency. The release tooling's
`@conventional-changelog/git-client` declares it as an optional peer, while commitlint also needs parser 5.x.
Without the explicit dependency, npm 11 can remove the release parser during Renovate's lockfile-only update,
producing a lockfile that npm 10 rejects during `npm ci`. Declaring parser 6.x keeps it resolvable for release
tooling and lets npm install commitlint's parser 5.x separately. After changing this dependency, verify a
lockfile-only update in a clean directory followed by `npm ci`, as well as the release tooling tests.

The bot uses `fix(deps)` commits, so an approved dependency-only update produces a **patch** release of Storage,
including Chrome-types-only updates and updates to a new upstream major version. Keep the `fix(deps): ...` title when
squashing; do not change it to `chore`, `feat`, or add a breaking marker. Other commits included in a release continue
Expand Down
144 changes: 49 additions & 95 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.

5 changes: 3 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,11 +81,12 @@
"@swc/core": "^1.7.0",
"@swc/jest": "^0.2.36",
"@testing-library/react": "^16.3.0",
"@types/chrome": "^0.1.12",
"@types/chrome": "^0.3.5",
"@types/jest": "^29.5.14",
"@types/node": "^22.18.4",
"@types/react": "^19.3.0",
"@types/react-dom": "^19.3.0",
"conventional-commits-parser": "^6.4.0",
"esbuild-fix-imports-plugin": "^1.0.22",
"eslint": "9.39.5",
"eslint-plugin-import-x": "4.16.1",
Expand All @@ -105,7 +106,7 @@
"typescript-eslint": "8.48.1"
},
"dependencies": {
"@addon-core/browser": "^0.9.0",
"@addon-core/browser": "^0.11.0",
"dequal": "^2.0.3"
},
"peerDependencies": {
Expand Down