Repository navigation
build(deps): refresh vulnerable website transitive dependencies - #956
Merged
Merged
Conversation
Update body-parser, qs, express, joi, and follow-redirects in the website lockfile to their patched releases. express 4.22.3 is required because 4.22.2 constrains qs to ~6.15.1 and therefore cannot resolve 6.16.1. Only website/pnpm-lock.yaml changes; launch-editor is left to #950.
PsiACE
approved these changes
Nov 19, 2026
Xuanwo
added a commit
that referenced
this pull request
Nov 19, 2026
…rser (#958) Refresh the website lockfile for the two transitive dependencies whose Dependabot security updates fail with `security_update_not_possible` (runs 44514732278 and 43795676825): | Package | Previous | Updated | Parent | Advisory | | --- | --- | --- | --- | --- | | `shell-quote` | 1.10.0 | 1.11.0 | `launch-editor@2.14.2` accepts `^1.10.0` | GHSA-pqg4-j6r4-53mv | | `fast-xml-parser` | 5.10.1 | 5.12.0 | `docusaurus-plugin-llms-builder@0.1.13` accepts `^5.2.3` | GHSA-474x-hrwr-fgx4 | `fast-xml-parser` 5.12.0 raises its own dependency ranges, so the lockfile also advances `@nodable/entities`, `fast-xml-builder`, `is-unsafe`, and `strnum` to compatible versions. Only `website/pnpm-lock.yaml` changes. This preserves #950's `launch-editor` entry and does not touch #956's separate refresh. Validation with Node 24.17.0 and the repository's `pnpm@11.8.0` on base `f5717cc`: - `pnpm install --frozen-lockfile` - `pnpm build` - `pnpm why` resolves one `shell-quote@1.11.0` under `launch-editor@2.14.2` and one `fast-xml-parser@5.12.0` under `docusaurus-plugin-llms-builder@0.1.13`.
Xuanwo
added a commit
that referenced
this pull request
Nov 19, 2026
The Azure live-test job in [#956](#956) failed at [job 135562203082](https://github.com/apache/reqsign/actions/runs/44514829652/job/135562203082) with `curl: (35) Send failure: Connection reset by peer` while polling the state of an already queued Azure Pipelines run. It failed before the Rust probe reported a result. The same status path succeeded on `main` and in #952, so this is a transient transport failure rather than a signing or credential regression. Retry GET status reads for the known run ID up to three times with a one-second delay, only for curl exit 35. The cleanup status read uses the same helper. The queue POST still runs once, and the cancel PATCH still runs at most once. Status reads use `--fail` so an error response body is never parsed or exposed, and the final curl exit status is preserved when retries are exhausted. Validation: `python3 .github/azure-live-tests/test_scripts.py` passes 14 tests, including one reset then success, exhausted retries retaining exit 35, and a cleanup reset followed by exactly one cancel. Shell syntax and Python compilation checks pass. No live Azure credentials were used.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refresh the website lockfile for patched transitive dependencies currently flagged by Dependabot. Only
website/pnpm-lock.yamlchanges.body-parserqsexpressbody-parser/qs; 4.22.2 constrainsqsto~6.15.1joifollow-redirectsResolved paths after the update:
webpack-dev-server@5.2.6->express@4.22.3->body-parser@1.20.9andqs@6.16.1@docusaurus/types@3.10.2and@docusaurus/utils-validation@3.10.2->joi@17.13.9http-proxy@1.18.1->follow-redirects@1.16.2#950 has already refreshed
launch-editorto 2.14.2; this PR preserves that entry and does not duplicate its changes. Other open alerts remain out of scope:serialize-javascript@6andminimatch@10are pinned by parent major constraints and need an override or framework upgrade rather than a compatible lock refresh.Validation with Node 24.17.0 and pnpm 11.8.0 on the current merge with
main:pnpm install --frozen-lockfilepnpm build