ci: resolve release preview PR from artifact metadata#755
Merged
Conversation
Store the PR number in the preview artifact and resolve it there first, falling back to workflow_run.pull_requests and open PR lookup by head SHA. 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-30)
### 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:** 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 |
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?
The comment workflow resolves the target PR via
listPullRequestsAssociatedWithCommitonworkflow_run.head_sha. That is fragile: merge commits can map to the wrong closed PR, and the comment workflow run itself always displaysmain's SHA (f7e190f), which is easy to misread as posting to the wrong commit.Issue Number: N/A
What is the new behavior?
pr-number.txtalongsidecomment.mdin the artifact.workflow_run.pull_requests→ open PR from head SHA.Does this PR introduce a breaking change?
Other information
Follow-up to #753. Investigated #752 where the comment workflow run showed
f7e190fbut the preview run used0402bab.Test plan
main