Uh oh!
There was an error while loading. Please reload this page.
Gate release on smoke; align CHANGELOG scaffold to an Unreleased section - #5
Merged
Merged
Conversation
…sed section Add smoke to the release job's needs wherever the smoke install-verification job exists (publish_to_pypi renders). No GitHub Release object is created unless the published package installed and imported. The added dependency renders only in the four publish_to_pypi combinations, where the smoke job is present; all eight flag combinations still yaml.safe_load with needs referencing only present jobs. Start template/CHANGELOG.md.jinja from `# Changelog` + `## Unreleased`, matching the new DOCS-STYLE Changelog section. The bootstrap release renames the heading to `## <version> - <date>` at tag time; the release job's awk gate matches on the version field, so a dated heading still extracts and a missing section still fails. SETUP.md.jinja's release step now instructs the rename. Document the changelog convention in DOCS-STYLE.md and state the install-verification gate in README.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Add
smoketo the release job'sneeds. The release job now depends on the post-publish install-verification job wherever it renders (the fourpublish_to_pypicombinations), so no GitHub Release object is created unless the published package installed and imported. All eight flag combinations stillyaml.safe_loadwithneedsreferencing only jobs present in that render.Start
template/CHANGELOG.md.jinjafrom# Changelog+## Unreleased, matching a new Changelog section inDOCS-STYLE.md. The bootstrap release renames the heading to## <version> - <date>at tag time; the release job's awk gate matches on the version field, so a dated heading still extracts and a missing section still fails.SETUP.md.jinja's release step instructs the rename.README.mdstates the install-verification gate in one clause.Follow-up context: pipe23-org/workspace#66.
🤖 Generated with Claude Code