Release v2.5.1 - #109
Merged
Merged
Conversation
npm already publishes on v* tags, but production GitHub Releases were created by hand. Mirror the develop pre-release job so pushing a version tag also generates a GitHub Release, skipping if one already exists. Co-authored-by: Yukai Huang <hi@yukai.dev>
Bump the package version and document tags, update-command permission flags, the permission-flag overwrite fix, skill and CodiMD docs, and develop-branch prereleases. Co-authored-by: Yukai Huang <hi@yukai.dev>
Yukaii
marked this pull request as ready for review
August 26, 2026 21:54
Use the matching CHANGELOG.md section as the release notes and still append GitHub's generated PR list so tagged publishes match v2.5.0-style history without requiring a manual GitHub UI draft. Co-authored-by: Yukai Huang <hi@yukai.dev>
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
2 participants
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
Prepares a 2.5.1 patch release from everything merged since
v2.5.0, and fills the GitHub Release gap in the publish workflow.Auto-publish vs GitHub Releases
v*tag runs tests andnpm publish. Pushes todevelopalready publish@betaprereleases.v2.5.0was created by hand in the GitHub UI. Only develop prereleases usedgh release create.CHANGELOG.mdsection, then append GitHub's generated PR list. If a release already exists (for example from the GitHub UI), the step is skipped.v2.5.1ondevelopshould publish npm and open the GitHub Release.masteris gone, so this targetsdevelopinstead of the oldrelease/*→masterflow.2.5.1 contents
--readPermission,--writePermission, and--permalinkon note update commands (Add tags support to notes and team-notes commands #97)codimd-cli(docs: update CodiMD compatibility notice to point to standalone codimd-cli #101)Test plan
CHANGELOG.mdfor the 2.5.1 entryv2.5.1ondevelopto publish npm and create the GitHub Release@hackmd/hackmd-cli@2.5.1on npm