Skip to content

[Snyk] Security upgrade express from 4.17.1 to 4.22.0 #163

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

Open
maniator wants to merge 1 commit into
base: next
Choose a base branch
from
Open

[Snyk] Security upgrade express from 4.17.1 to 4.22.0 #163

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
2 changes: 1 addition & 1 deletion docs/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@
"docsearch.js": "^2.6.3",
"doctrine": "^3.0.0",
"emotion-theming": "^10.0.27",
"express": "^4.17.1",
"express": "^4.22.0",
Copy link

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

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

express was bumped in docs/package.json, but the workspace lockfile still resolves express to 4.17.1 (and qs 6.7.0). Please regenerate and commit the updated root yarn.lock so installs/CI actually pick up express@^4.22.0 and the vulnerability fix takes effect.

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Feb 12, 2026

Choose a reason for hiding this comment

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

P2 Badge Commit lockfile update for express bump

This dependency bump is incomplete because docs/package.json now requires express ^4.22.0, but the committed lockfile still resolves express@^4.17.1 to 4.17.1 (yarn.lock:7425). That leaves the checked-in dependency graph on the vulnerable version, so lockfile-based auditing/reproducibility workflows will not reflect the intended security fix until yarn.lock is regenerated and committed alongside this change.

Useful? React with 👍 / 👎.

"fg-loadcss": "^2.0.1",
"final-form": "^4.18.5",
"flexsearch": "^0.6.30",
Expand Down