Repository navigation
fix: resolve proxy-addr to 2.0.8, 2.0.7 is curation-blocked - #1409
Conversation
Artifactory returns 403 for proxy-addr@2.0.7, which breaks cold-cache installs (the release build/publish/deploy-cdn jobs don't restore the yarn cache). Same approach as the axios and is-email resolutions.
🌙 Earthly Lunar❌ 1 Failing
✅ 2 Passing |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Please upload reports for the commit 2706f7a to get more accurate results. Additional details and impacted files@@ Coverage Diff @@
## master #1409 +/- ##
=======================================
Coverage 91.59% 91.59%
=======================================
Files 128 128
Lines 4162 4162
Branches 1036 1036
=======================================
Hits 3812 3812
Misses 350 350
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
looks good |
Summary
Artifactory returns 403 for
proxy-addr@2.0.7, which fails a cold-cacheyarn install. That broke the 1.84.4 release run (https://github.com/segmentio/analytics-next/actions/runs/44124753244): thebuildjob failed, sopublishanddeploy-cdnnever ran.testpassed in that run only because it restores the yarn cache (cache: 'yarn');build,publishanddeploy-cdninstall from scratch.proxy-addris a transitive dependency of the rootexpress@^4.18.2devDependency, which pins~2.0.7. 2.0.8 (2026-09-15) has identical dependencies, so this adds a resolution, the same approach as the axios (#1386) and is-email (#1388) fixes.Changes
package.json:"proxy-addr@~2.0.7": "^2.0.8"inresolutionsyarn.lock:proxy-addr2.0.7 to 2.0.8, nothing elseTest plan
yarn install --immutablepasses locally;yarn why proxy-addrshows express 4.18.2 resolving to 2.0.8yarn buildand the pre-push typecheck passtestjob confirms it.publish.ymlviaworkflow_dispatchon master and approve theproductiongate to release 1.84.4No changeset: this only changes a root devDependency resolution, so
changeset-botreporting none is expected.