Normalize Markdown after version bumps. - #33
Merged
Merged
Conversation
samuel-williams-shopify
deleted the
codex/normalize-markdown-on-release
branch
October 5, 2026 10:15
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.
The version-bump hook now normalizes the standard project Markdown files after updating release metadata and generated Readme content.
Previously the hook refreshed project files without normalizing their Markdown. It now includes
license.md,readme.md,releases.md, and Markdown files recursively under the publiccontext/directory. The.agents/context/directory remains outside the selection. The Bake package linksbake-markdown, and the setup, conventions, and releasing guides document this behavior.