fix(IDS-7281): bump axios to 1.16.1 and rebuild bundle 2.13.4#447
Open
hamzabenali-okta wants to merge 1 commit into
Open
fix(IDS-7281): bump axios to 1.16.1 and rebuild bundle 2.13.4#447hamzabenali-okta wants to merge 1 commit into
hamzabenali-okta wants to merge 1 commit into
Conversation
axios ships in the extension's client bundle, so this lockfile bump is a genuine fix that clears SEC-29850. All deps resolved from a0us.jfrog.io. @hapi/content and fast-xml-parser are transitive deps of verquire externals (@hapi/hapi, @aws-sdk/client-s3) with no runtime effect here, so their override "fix" was cosmetic and is dropped. The real remediation is tracked in IDS-7307 (webtask-monorepo). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
✏️ Changes
Bumps axios to
1.16.1(pinned, was^1.15.0) to pull in upstream security fixes. axios ships in the extension's client bundle, so this lockfile bump is a genuine runtime fix.package.json:axiospinned to1.16.1; extensionversionbumped2.13.3→2.13.4.package-lock.json: regenerated against our private registry. Only the axios subtree changed (axios +agent-base,https-proxy-agent).server/plugins/html.js:EXTENSION_VERSION→2.13.4.dist/+build/bundle.js+dist/manifest.json: rebuilt as2.13.4artifacts.Out of scope:
@hapi/contentandfast-xml-parserare transitive deps of verquire externals (@hapi/hapi,@aws-sdk/client-s3) resolved at runtime by the webtask platform. Bumping them viapackage.jsonoverridesonly rewrites this repo's lockfile with no runtime effect, so those cosmetic overrides were dropped. Their remediation is tracked separately.🎯 Testing
npm test— 523 unit tests passing.npm run buildcompiles cleanly and produces the2.13.4artifacts. Webtask verification pending pre-deploy.✅ This change has unit test coverage
✅ This change has been tested in a Webtask
🚫 This change has integration test coverage (dependency bump only; no integration surface changed)
🚫 This change has been tested for performance (transport library patch bump, no perf-sensitive path changed)
🚀 Deployment
✅ This can be deployed any time
🎡 Rollout
After deploy, verify the extension loads and the client bundle (
auth0-authz.ui.2.13.4.js) is served, confirming axios1.16.1is bundled.🔥 Rollback
We will rollback if the extension fails to load or client-side requests regress after the axios bump.
📄 Procedure
Revert this PR and redeploy the previous
2.13.3bundle.