chore: update dependencies and changelog for v1.31.2 - #577
Conversation
Bumps runtime dependencies axios (^1.18.1 -> ^1.20.0) and qs (^6.15.2 -> ^6.16.0), plus dev dependencies @babel/eslint-parser, @slack/bolt, @types/lodash, jest, nock, ts-jest and webpack. npm audit across the dependency tree before and after: before 17 vulnerabilities (3 critical, 6 high, 7 moderate, 1 low) after 10 vulnerabilities (3 critical, 1 high, 5 moderate, 1 low) Seven resolved, five of them high severity. The qs advisory is the consumer-facing one, since qs is a runtime dependency. The ten that remain are all dev-only (babel-traverse, mocha, nyc, istanbul, serialize-javascript, uuid, diff, mochawesome) and are not shipped. Verified with npm run lint (clean) and npm run test:unit (686 passing). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ 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. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The PR description conflicts with the diff (it states package.json was already 1.31.2, but this PR bumps it), and should be corrected for release accuracy.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
This PR prepares the v1.31.2 dependency-update release for @contentstack/management by bumping runtime/dev dependencies, updating the lockfile, and adding a matching changelog entry.
Changes:
- Bump package version to 1.31.2 and update runtime deps (
axios,qs) plus several dev deps. - Refresh
package-lock.jsonto reflect the updated dependency graph. - Add the v1.31.2 entry to
CHANGELOG.md.
| File | Description |
|---|---|
| package.json | Updates SDK version to 1.31.2 and bumps runtime/dev dependency ranges. |
| package-lock.json | Regenerates lockfile to match updated dependency versions and transitive tree. |
| CHANGELOG.md | Adds the v1.31.2 release note entry. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The Coverage report step (lucassabreu/comment-coverage-clover) creates a comment on the pull request, which is a write operation. unit-test.yml declared no permissions block, so the job received the repository default. The job log for run 35718905177 records what the token actually held: GITHUB_TOKEN Permissions Contents: read Metadata: read Packages: read All read, no write, so the POST to the issue-comments endpoint returned 403 "Resource not accessible by integration". Build, tests and the dorny/test-reporter step all succeeded; only the coverage comment failed. This affects every run since 2026-08-02, including on development and master. The last successful run was 2026-07-29. Declaring a permissions block sets unlisted scopes to none, so contents: read is included for actions/checkout. checks: write is deliberately not granted: the test-reporter step is currently succeeding without it. Mirrors back-merge-pr.yml and sca-scan.yml, which already declare the same two scopes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
|
Coverage report for commit: 4df953b Summary - Lines: 82.77% | Methods: 95.77% | Branches: 65.89%
🤖 comment via lucassabreu/comment-coverage-clover |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |



Summary
Dependency update release for v1.31.2, with the changelog entry added. Also fixes a pre-existing CI permissions failure that was blocking this and every other PR.
1. Dependency updates (
abb7104)Runtime
axiosqsDev
@babel/eslint-parser,@slack/bolt,@types/lodash,jest,nock,ts-jest,webpackSecurity impact
npm auditacross the full dependency tree, before and after:Seven resolved, five of them high severity.
The
qsadvisory is the consumer-facing one —qsis a runtime dependency, so that fix reaches anyone installing the SDK.axiosshowed no advisory in either tree; that bump is maintenance.The ten remaining are all dev-only (
babel-traverse,mocha,nyc,istanbul-lib-processinfo,serialize-javascript,uuid,diff,mochawesome) and are not shipped to consumers. Clearing them means upgrading the test toolchain — larger than this PR should carry.Changelog
2. CI permissions fix (
47dd3d2)The
Coverage reportstep was failing with:unit-test.ymldeclared nopermissions:block, so the job received the repository default. The job log for run35718905177records what the token actually held:All read, no write — so the
POSTto the issue-comments endpoint returned 403. Build, tests anddorny/test-reporterall succeeded; only the coverage comment failed.Fix is three lines:
Notes:
developmentandmaster. Last success was 2026-07-29.contents: readis required because declaring apermissionsblock sets unlisted scopes tonone, which would breakactions/checkout.checks: writeis deliberately not granted — thedorny/test-reporterstep is currently succeeding without it.back-merge-pr.ymlandsca-scan.yml, which already declare these same two scopes.Verification
npm run lint— cleannpm run test:unit— 686 passingnpm ciinstalls cleanly from the updated lockfileunit-test.ymlre-parsed withjs-yamlafter the editFollow-ups not included here
lucassabreu/comment-coverage-clover@mainis pinned to a moving branch. Now that it haspull-requests: write, pinning to a SHA is worth a separate decision.actions/checkout@v2andactions/setup-node@v3are several majors behind; the run log warns about Node 20 deprecation.🤖 Generated with Claude Code