Repository navigation
DX | 02-11-2026 | Release - #102
Merged
Merged
Conversation
chore: back-merge master into development
chore: back-merge master into development
DX | 03-08-2026 | Release | Back-merge
Publish on release:published from release.yml so the npm trusted publisher can be keyed on the filename, drop the NPM_TOKEN passed to JS-DevTools/npm-publish 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. The tarball is attached to the release from a separate job with gh release upload instead of the archived upload-release-asset action. 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 now reaches the upload step through the RELEASE_TAG env variable instead of being interpolated into the shell line (GitHub Actions script-injection hardening). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
overrides.brace-expansion: 5.0.9 -> 5.0.12 Fixes SNYK-JS-BRACEEXPANSION-20244948, -20244950, -20244952 (via rimraf > glob > minimatch). package-lock.json regenerated from a clean install. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
chore(release): publish to npm with trusted publishing
…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
ℹ️ 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 |
development was at 2.1.14, but the last version published to npm is 2.1.11. 2.1.12 never reached npm (its release failed at the publish step) and 2.1.13 and 2.1.14 were bumped by Snyk-fix PRs without a release.
Set development to 2.1.12 so the next release is a single patch on top of 2.1.11.
- package.json / package-lock.json: version 2.1.14 -> 2.1.12
- package-lock.json: updates within existing ranges for @babel/{generator,helper-string-parser,parser,traverse,types}, baseline-browser-mapping, browserslist, caniuse-lite, electron-to-chromium, node-releases and ts-jest
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
chore: set version to 2.1.12 and refresh lock file
🔒 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 |
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 #99): runs onrelease: published,id-token: write, Node 24 and latest npmpackage.jsonand passes it via envbrace-expansionoverride raised to5.0.12masterintodevelopmentNotes
package.jsonis still2.1.14, so merging does not publish anything. Publishing needs a version bump and a GitHub release.🤖 Generated with Claude Code