Repository navigation
DX | 29-09-2026 | Release - #151
15 commits merged into
Conversation
chore: back-merge main into development
chore: back-merge main into development
chore: back-merge main into development
Brings back-merge branch up to date with development so main can be back-merged cleanly (DX-20927). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DX-20927 | Back-merge main into development
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
✅ 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 |
Publish on release:published from release.yml so the npm trusted publisher can be keyed on the filename, drop NODE_AUTH_TOKEN in favour of id-token: write (OIDC), run on Node 24 with npm@latest (trusted publishing needs npm >= 11.5.1), check out the release tag without persisted credentials. GitHub pre-releases go to the beta dist-tag. The GitHub Packages job gains the packages: write permission it was missing and keeps publishing with the job's own token. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Refuse to publish when the release tag is not "v" + the package.json version, so a tag cut on the wrong commit cannot publish an older version under a newer tag. The GitHub Packages job now uses the same beta/latest dist-tag rule as the npm job, so a GitHub pre-release never becomes latest on either registry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Snyk (snyk test --all-projects): 13 issues (8 high, 5 medium, all axios 1.18.1) -> 0. Regenerated package-lock.json (axios 1.18.1 -> 1.20.0). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…velopment chore: back-merge main into development
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
Lock file regenerated (fixed 3 on its own: body-parser high, markdown-it high, fast-uri moderate; all dev-only). Direct upgrades: none (no patch or minor bump clears a finding) Overrides: none (remaining transitive fixes are cross-major) Vuln count: snyk 0 → 0, npm audit 13 → 10. Build verified passing. .talismanrc: package-lock.json checksum replaced by a filecontent/base64content ignore so lock regens stop tripping talisman. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The check-version-bump workflow requires package.json to be above the latest tag once a PR changes it; this PR's Snyk lock fix does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Coverage report step posts a PR comment, which the default read-only
GITHUB_TOKEN refuses ("Resource not accessible by integration"), so Build &
Test failed although every test passed. Grant pull-requests: write on the job
and keep contents: read for the checkout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore(release): publish to npm with trusted publishing
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
|
Coverage report for commit: 1503e2d Summary - Lines: 85.93% | Methods: 96.08% | Branches: 67.22%
🤖 comment via lucassabreu/comment-coverage-clover |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
No description provided.