Skip to content

Relock dependencies to satisfy the package feed cooldown - #3711

Merged
Jake Bailey (jakebailey) merged 2 commits into
microsoft:v2from
jakebailey:feed-proxy-relock
Nov 20, 2026
Merged

Jake Bailey (jakebailey) merged 2 commits into
microsoft:v2from
jakebailey:feed-proxy-relock

Conversation

@jakebailey

Copy link
Copy Markdown
Member

I screwed up and forgot about the cooldown. Relock to slightly older deps. No audits regress, thankfully.

Also, fix a missed node version in the release pipeline.

The internal package feed only serves versions that have been published
for at least seven days, and the audit update locked several packages
newer than that, so installs from the feed fail with 404s. Re-resolve
those packages to the newest versions the feed serves.

DOMPurify 3.4.18 is one of them; 3.4.17 has no known advisories, so the
override floor moves down to it.
The repository requires Node 24, but the release pipeline was still
installing Node 22, so it runs with an unsupported engine.
@jakebailey
Jake Bailey (jakebailey) merged commit 0dbca87 into microsoft:v2 Nov 20, 2026
9 checks passed
@jakebailey
Jake Bailey (jakebailey) deleted the feed-proxy-relock branch November 20, 2026 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants