chore: update axios to version 1.15.0#255
Merged
Merged
Conversation
- Upgraded axios from 1.13.5 to 1.15.0 in package-lock.json and package.json. - Updated proxy-from-env dependency to version 2.1.0. - Introduced a new package '@naap/services-rest-client' with its own package-lock.json, utilizing axios 1.15.0.
|
|
📝 WalkthroughWalkthroughThe pull request updates the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
eliteprox
enabled auto-merge (squash)
April 9, 2026 21:15
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
package.json (1)
70-70: Prefer exact version inoverridesfor deterministic installs.The
axiosoverride at line 70 uses^1.15.0, which allows future 1.x upgrades. For workspace reproducibility and consistent CI behavior, pin this to an exact version like the other overrides in the same block.♻️ Proposed change
- "axios": "^1.15.0", + "axios": "1.15.0",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 70, Update the axios entry in the overrides block to use an exact version instead of a caret range: replace the current "axios": "^1.15.0" override with the exact pinned version "axios": "1.15.0" so installs are deterministic and match the other overrides.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@package.json`:
- Line 70: Update the axios entry in the overrides block to use an exact version
instead of a caret range: replace the current "axios": "^1.15.0" override with
the exact pinned version "axios": "1.15.0" so installs are deterministic and
match the other overrides.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d1155e4b-008b-4ba9-9a5b-f9355de6bba9
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.json,!package-lock.jsonpackages/services/rest-client/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.jsonpackages/services/rest-client/package.json
seanhanca
added a commit
that referenced
this pull request
Jul 16, 2026
Record the composite bearer webhook fix PR so John can review and deploy. Co-authored-by: Cursor <cursoragent@cursor.com>
seanhanca
added a commit
that referenced
this pull request
Jul 17, 2026
Live probes show pymthouse#255 still OPEN with merge conflicts, validate regressed to token-bundle (no composite endpoint), and SDK path fails with IncompleteRead after 401-class webhook auth. Documents minimum one-shot deploy set for John and latent post-#255 blockers. Co-authored-by: Cursor <cursoragent@cursor.com>
seanhanca
added a commit
that referenced
this pull request
Jul 18, 2026
Tested the app_98575870 signer-session bundle directly against the test-production signer, bypassing the NaaP validate / Vercel env blocker. Key findings: - Composite bearer PASSES the remote-signer webhook auth (/sign-orchestrator-info 200; /generate-live-payment returns a real, valid net.Payment proto) -> 401 "not a JWT" is gone; #255 no longer the blocker for the composite path. - submit_byoc_job flux-schnell/flux-dev fail at the orchestrator with HTTP 400 "Could not parse payment" -> ProcessPayment (on-chain ticket validation) rejects a valid, recipient-correct ticket. Likely sender reserve unfunded / ticket-param mismatch on test-production. Owner: John. - OpenMeter increments at signer payment-gen (platform_ingest), decoupled from orch success (+4 reqs / +4 µUSD, floor-rate; no image). Adds scripts/run50-direct-signer-probe.py (env-only, no secrets). Co-authored-by: Cursor <cursoragent@cursor.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.
Summary
This change unblocks failing CI checks by bumping axios from 1.13.5 to >1.15.0
Changes
Type
Plugin(s) Affected
Checklist
npm run lint)npm run build)Breaking Changes
None
Screenshots / Recordings
Summary by CodeRabbit