Conversation
Tag pushes can lack the release CHANGELOG section while main has it; checking out origin/main fails when generated api-version differs on the runner. Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
unjica
added a commit
that referenced
this pull request
Jul 12, 2026
…-after-383 chore: sync develop with main after PR #383
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.
Summary
87fba02): release-email workflow overlaysCHANGELOG.mdfromorigin/mainviagit show … > CHANGELOG.mdinstead ofgit checkout origin/main, so tag checkout and install steps stay on the release commit.Context
developbut not yet onmain.developis one commit ahead ofmain; diff is only.github/workflows/release-email.yml.Test plan
mainworkflow step usesgit show origin/main:CHANGELOG.md > CHANGELOG.md.Made with Cursor