ci: create GitHub release after pushing version tags#761
Merged
Conversation
Run the semver github target as a dedicated publishment step after tags are pushed so gh release create targets refs that exist on the remote. Related to #244 Co-authored-by: Cursor <cursoragent@cursor.com>
Release preview
PR title: Semantic commit (PR title)✅ Valid conventional commit Version
Changelog preview## [9.2.0](https://github.com/bikecoders/ngx-deploy-npm/compare/ngx-deploy-npm-9.1.0...ngx-deploy-npm-9.2.0) (2026-05-31)
### Features
* **ngx-deploy-npm:** extend checkExisting with skip mode and checkTag ([#749](https://github.com/bikecoders/ngx-deploy-npm/issues/749)) ([1250a91](https://github.com/bikecoders/ngx-deploy-npm/commit/1250a9189f46e62e56b03cde76522663c9918467))
* **ngx-deploy-npm:** forward npm publish passthrough flags ([#751](https://github.com/bikecoders/ngx-deploy-npm/issues/751)) ([371751b](https://github.com/bikecoders/ngx-deploy-npm/commit/371751b0f41fac6acb6597d6860ae4a88f86aecc))
* **ngx-deploy-npm:** log post-publish summary with streaming tarball size ([#750](https://github.com/bikecoders/ngx-deploy-npm/issues/750)) ([dbfe288](https://github.com/bikecoders/ngx-deploy-npm/commit/dbfe288a69f52f3749a6d80d4c54ddc87ea8afb0)), closes [#749](https://github.com/bikecoders/ngx-deploy-npm/issues/749)
### Bug Fixes
* **ngx-deploy-npm:** apply packageVersion transiently during dry-run ([#752](https://github.com/bikecoders/ngx-deploy-npm/issues/752)) ([cf7013f](https://github.com/bikecoders/ngx-deploy-npm/commit/cf7013f6311c1cbe3ab81dfe08b366ac323265df))
* **ngx-deploy-npm:** resolve open SonarCloud static analysis issues ([#746](https://github.com/bikecoders/ngx-deploy-npm/issues/746)) ([599ac29](https://github.com/bikecoders/ngx-deploy-npm/commit/599ac2971841cdec6fd720428ed2ae5546492ed5))Generated by CI (PR Release Preview). Actual release runs on merge via publishment.yml. Notes: Preview uses only the PR title (squash merge). Changes outside |
7 tasks
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
1 participant
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.
PR Checklist
Please check if your PR fulfills the following requirements:
What is the current behavior?
After #759, the publishment workflow runs
@jscutlery/semver:githubas apostTargetofnx version, which creates the GitHub release before version tags are pushed to the remote. That ordering can causegh release createto run against tags that only exist locally at that point.Issue Number: #244
What is the new behavior?
The
githubtarget is removed from the semverpostTargetschain. The publishment workflow now runsnpx nx github ngx-deploy-npmin a dedicated step afterad-m/github-push-actionpushes commits and tags, withGITHUB_TOKENscoped to that step.Does this PR introduce a breaking change?
Other information
Follow-up to #759. Related to #244.