feat: automate releases with semantic-release and npm OIDC trusted publishing#272
Merged
Conversation
…ublishing Replace the manual release process with semantic-release. - Add Release workflow (workflow_dispatch) that runs semantic-release, authenticating to npm via OIDC trusted publishing (no NPM_TOKEN), scoped to the production environment and running on Node 24. - Add Lint PR workflow validating PR titles as Conventional Commits, which semantic-release uses to determine versions and generate release notes. - Add scripts/prepublish-only.js to block publishing from local machines. - Configure semantic-release plugins in package.json and replace the prepublishOnly CI hook with the guard plus a prepack build step. - Document the Conventional Commits and automated release flow in CONTRIBUTING.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Release job: pin Node 26 (bundles npm 11.16.0 >= 11.5.1) and drop the manual npm upgrade step it makes redundant. - CI job: bump Node from 16 to 24 so the dependency tree, including semantic-release (engine ^22.14.0 || >= 24.10.0), is compatible. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tsotnikov
approved these changes
Jun 11, 2026
Address review feedback on #272. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
atabel
approved these changes
Jun 12, 2026
andyindahouse
approved these changes
Jun 12, 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
Migrate from the manual release process to automated releases with semantic-release, publishing to npm via OIDC trusted publishing.
This is a cleaned-up, scope-reduced take on #183: it keeps only the release-automation changes.
Changes
.github/workflows/release.yml): manual-dispatch job runningsemantic-release. Authenticates to npm via OIDC trusted publishing (id-token: write, noNPM_TOKEN), runs on Node 26, and is scoped to theproductionenvironment..github/workflows/lint-pr.yml): validates PR titles against the Conventional Commits format (fix,feat,chore,revert), which semantic-release uses to determine the next version and generate release notes.scripts/prepublish-only.js): blocks publishing from local machines and points to the Release action.prepublishOnlyCI hook with the guard plus aprepackbuild step..github/workflows/ci.yml): bumps Node from 16 to 24 so the dependency tree (includingsemantic-release) is compatible.Related
masterrequired status check names (Node 24) and brings theproductionenvironment under Terraform management. Apply together with this PR.Required configuration before first release
@tef-novum/webview-bridgepackage on npmjs.com: repositoryTelefonica/webview-bridge, workflowrelease.yml, environmentproduction.FLOW_GITHUB_TOKENsecret is available to theproductionenvironment (used by@semantic-release/gitto push the changelog and version commit past branch protection).