ci: migrate release automation from semantic-release to release-please - #391
Merged
Merged
Conversation
kgogov
changed the title
kgogov
marked this pull request as ready for review
September 24, 2026 14:03
…et name is correct
- pr-title-lint: drop 'synchronize' (title unchanged on push; 'edited' covers it) - release: npm ci --ignore-scripts + explicit tsc + grunt dist, so the artifact isn't built twice (postinstall already runs tsc + grunt dist)
kgogov
force-pushed
the
feat/release-please-migration
branch
from
September 25, 2026 07:51
d9fcc4f to
8d727ef
Compare
PetyaMarkovaBogdanova
self-requested a review
September 25, 2026 07:57
flovogt
reviewed
Sep 25, 2026
PetyaMarkovaBogdanova
approved these changes
Sep 25, 2026
PetyaMarkovaBogdanova
left a comment
PetyaMarkovaBogdanova
left a comment
Contributor
There was a problem hiding this comment.
Residual risk
The old workflow ran grunt test immediately before release; the new workflow only builds and uploads. This is acceptable if CI status checks are required on the Release PR, but the release workflow itself no longer enforces tests.
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
3 participants
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.
What & why
Replaces the semantic-release pipeline (broken since Aug —
@semantic-release/gitpushes the version bump straight to protectedmaster→ GH006) with release-please, which opens a Release PR instead of pushing. No GitHub App, PAT, or bypass actor — the defaultGITHUB_TOKENis enough.Changes
release-please-config.json+.release-please-manifest.json(seed1.10.0)release.yml:release-please-action@v5on push tomaster; on Release-PR merge, buildgrunt dist+gh release upload, gated onrelease_created.releaserc.json,scripts/update-version.js, 7 devDeps)bootstrap-shaanchors adoption to the 1.10.0 release → first PR is1.11.0, not a full-history2.0.0include-component-in-tag: falsekeeps plainvX.Y.Ztags (matches history) + correct asset nameci.yml/release.ymlactions to@v7, pin node 24pr-title-lint.yml— enforces Conventional Commits on PR titles, so squash-merge commit subjects stay parseable by release-please and land in the changelogValidation
release-please --dry-run→ clean1.11.0+ changelogv1.11.0+ assetui5inspector-v1.11.0.zipuploaded ✓