Repository navigation
DX | 03-08-2026 | Release - #64
Conversation
chore: back-merge master into development
chore: back-merge master into development
chore: back-merge master into development
✅ 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 |
DX | 03-08-2026 | Release | Back-merge
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
789943a to
426bb66
Compare
DX | 12-08-2026 | Release | Back-merge
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
Publish on release:published with plain npm publish and id-token: write (OIDC) instead of JS-DevTools/npm-publish with NPM_TOKEN, run on Node 24 with npm@latest (trusted publishing needs npm >= 11.5.1), install with npm ci, check out the release tag without persisted credentials, and drop the post-publish gh release create step: the release is the trigger now, and the step failed with 403 under the read-only job token. GitHub pre-releases go to the beta dist-tag. .nvmrc pins 24 to match the publish job. 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 tag reaches the check through an env variable, never through a shell line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…indings undici: ^7.29.0 -> ^7.29.1 (lock resolves 7.29.0 -> 7.30.0) brace-expansion override: 5.0.9 -> 5.0.12 Snyk findings: 13 -> 0 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Lock file regenerated (fixed 18 on its own). Direct upgrades: undici ^7.30.1, jest ^29.7.0, @types/node 10.17.60, supertest 3.4.2, tslint 5.20.1, typescript ^5.9.3 Overrides: brace-expansion 5.0.9 -> 5.0.12 Vuln count: snyk 21 -> 0, npm audit 34 -> 34. Build verified passing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…evelopment chore: back-merge master into development + Snyk fixes
✅ 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 |
# Conflicts: # package-lock.json # package.json
chore(release): publish to npm with trusted publishing
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
development was at 2.3.9 while the last published version on npm is 2.3.7 and master is at 2.3.8 (never published). Set development to 2.3.8 so the next release is a single patch on top of 2.3.7. Only package.json and package-lock.json change (version fields). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
chore: set version to 2.3.8
🔒 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 |
🔒 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 |
Security