Repository navigation
DX | 02-11-2026 | Release - #78
Merged
Merged
Conversation
chore: back-merge master into development
chore: back-merge master into development
chore: back-merge master into development
Publish on release:published so the npm trusted publisher keyed on release.yml can be used, 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, keep the explicit build-ts step. GitHub pre-releases go to the beta dist-tag. 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>
…e.yml github-release.yml created the GitHub release with GITHUB_TOKEN on every version bump pushed to master. Events raised by that token do not start other workflows, so with publishing on release: published a bot-created release would never run release.yml and npm would silently miss the version. Releases are created by a person instead (as since v1.1.3), and release.yml now attaches the npm pack tarball after a successful publish. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Regenerated package-lock.json (clean npm install); no package.json change. qs 6.15.3 -> 6.16.0 (via body-parser) Fixes SNYK-JS-QS-19432017 and SNYK-JS-QS-19432019 Snyk: 2 medium findings -> 0 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…evelopment chore: back-merge master into development
Lock file regenerated (fixed 2 on its own). Direct upgrades: body-parser ^2.3.0 -> ^2.4.0 (library floor raise; installs body-parser 2.4.0 and qs 6.16.1) Overrides: none .talismanrc: package-lock.json checksum entry replaced by a filecontent/base64content ignore so lock regens stop tripping Talisman. Vuln count: snyk 2 -> 0, npm audit 1 -> 0. Build verified passing. 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>
chore(release): publish to npm with trusted publishing
✅ 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
ℹ️ 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 |
Raise the minimum versions of direct dependencies and refresh package-lock.json. dependencies: - debug ^4.3.5 -> ^4.4.3 devDependencies: - @types/basic-auth ^1.1.2 -> ^1.1.8 - @types/node ^10.12.2 -> ^10.17.60 - jest ^29.0.3 -> ^29.7.0 - rimraf ^2.6.2 -> ^2.7.1 - supertest ^3.3.0 -> ^3.4.2 - typescript ^4.2.0 -> ^4.9.5 package.json version stays at 1.1.5. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
chore: bump dependencies
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
reeshika-h
approved these changes
Nov 2, 2026
Aravind-Kumar-cstk
approved these changes
Nov 2, 2026
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
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
Release PR: promotes
developmenttomaster. The main change is DX-27614 —release.ymlpublishes to npm with OIDC trusted publishing (noNPM_TOKEN). It has to be onmaster, where releases are cut from.What's included
release.yml(chore(release): publish to npm with trusted publishing #73): runs onrelease: published,id-token: write, Node 24 and latest npmpackage.jsongithub-release.ymldropped; the tarball is attached inrelease.ymlqsvulnerabilities resolved via lock file refresh, 1 dependency bumped for Snyk1.1.4→1.1.5Notes
v1.1.5is published.🤖 Generated with Claude Code