The release note generated by action-gh-release includes older changes than the selected version
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
When I use action-gh-release, some older changes exist.
For example, I released v0.46.0 from v0.45.4. I expected the release note to include changes from v0.45.4 to HEAD commit, but there were some changes created at older than v0.45.4.
https://github.com/pipe-cd/pipecd/pull/4775#issuecomment-1928719219
Maybe it looks like changes from v0.45.0 to HEAD commit because the last one is the next to the merged commit for v0.45.0.
https://github.com/pipe-cd/pipecd/commits/master/?after=49627aa0e3dcd29c30d3f251813ac36f077ebb25+104
What you expected to happen:
We hope to include the correct changes like from v0.45.4 to v0.46.0.
How to reproduce it:
Environment:
pipedversion:control-planeversion:- Others:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how action-gh-release determines the previous and selected version tags for generated release notes. Compare the changes included when releasing v0.46.0 from v0.45.4 with the expected v0.45.4-to-v0.46.0 range, using the linked release and commit history as examples. Done means older changes are excluded from the generated notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100