Repository navigation
ci: install wrangler from the in-cluster Verdaccio npm proxy, pinned - #82
Merged
mattmattox merged 1 commit intoOct 18, 2026
Merged
Conversation
All three deploy jobs ran an unpinned `npm install -g wrangler` straight from registry.npmjs.org. They now install wrangler@4.86.0 (the version the deploys already resolved to, run 39008946036) through the Verdaccio pull-through proxy in a1-ops-prd (http://verdaccio.npm-proxy.svc.a1-ops-prd.local/, where self-hosted-linux runs). The step fails visibly if the mirror is down or served no fetches ("fetch GET 200 <mirror>" guard), rather than quietly going upstream. Proven in-cluster: install rc=0, 129 fetches from Verdaccio, wrangler --version 4.86.0. Refs: cluster-services-1030
mattmattox
deleted the
chore/npm-verdaccio-wrangler-cluster-services-1030
branch
October 18, 2026 01:21
This branch was successfully deployed
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.
What
NPM_REGISTRY=http://verdaccio.npm-proxy.svc.a1-ops-prd.local/,WRANGLER_VERSION=4.86.0.npm install -g wrangler@${WRANGLER_VERSION} --registry=$NPM_REGISTRY --loglevel=httpand require at least onefetch GET 200 <mirror>line. Otherwise the step fails (mirror down, or the mirror wasn't actually used); it does not quietly go upstream.Why
cluster-services-1030 (parent 1027): build fetches should come from a cache we run. Verdaccio (cluster-services
npm-proxy/, 2 replicas, PDB, critical 0-ready alert) already serves TaskForge CI. All jobs here run onself-hosted-linuxin a1-ops-prd.Pin: the old step was unpinned (it took the latest wrangler). 4.86.0 is what the last successful deploy (run 39008946036) used, so this changes the source, not the version. Bump
WRANGLER_VERSIONdeliberately.Verified
From a node:22-alpine pod in a1-ops-prd, with the same command: rc=0, 129 fetches served by Verdaccio,
wrangler --version= 4.86.0.Refs: cluster-services-1030