Pin axios in framework-dist runtime package#13454
Conversation
Co-authored-by: Eslam λ Hefnawy <eslam@serverless.com>
📝 WalkthroughWalkthroughAdded an Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Hotfix for the runtime release tarball installed by the binary updater.
Root cause:
packages/framework-dist/package.jsonships without a lockfile.npm install --no-audit --no-fund --no-progressinpackage/.@aws-sdk/signature-v4-crtpulls inaws-crt, which depends onaxiosvia^1.12.2.axios@1.14.1to be selected during the incident window.Fix:
overrides.axios = 1.13.6topackages/framework-dist/package.jsonso the extracted runtime package installs a known safe axios version regardless of the transitive semver range.Validation:
npm install --package-lock-onlyresolved axios from the transitive semver range.axios@1.13.6.packages/framework-distand confirmed the generated tarball contains the override inpackage/package.json.Closes: #13453
Summary by CodeRabbit