You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write the generated notes where the release can actually commit them
Two bugs, both fatal to the generate-notes path.
write_changelog_section ran during preflight, so it dirtied a tracked
file before the release-commit step, which refuses to run on an unclean
tree. Every generated-notes release would have died there. And nothing
staged CHANGELOG.md anyway, so the section would never have reached main.
The write now happens in the release-commit step and is staged with the
version bump, which also puts it in DOC_FILES before the binaries build.
The insertion point matched the first `## [` of any kind, which is the
live `## [Unreleased]` heading — the new release sorted above it and
stranded its contents below every future release. It now targets the
first versioned header, and warns when Unreleased still has content,
since nothing renames it any more.
previous_tag is gone. The script fetches with --no-tags and never
refreshes tags, so deriving the previous tag locally would replay
already-released pull requests from a stale clone. GitHub derives it from
release history instead. That also removes a set -e trap: the pipeline
returned 1 on a first release and only survived because command
substitution under `||` suspends errexit.
CL-7888
0 commit comments