Repository navigation
chore: prepare v2.3.0 release - #222
Merged
Merged
Conversation
Co-authored-by: Weimeng Chen <MikeChenWM@users.noreply.github.com>
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
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.
Why
Mike asked for the HTML document CLI to ship. #221 is on main, and the published wheel is still 2.2.0, so this prepares the 2.3.0 release the same way v2.1.0 was prepared.
Changes
Minor bump, 2.2.0 to 2.3.0. The only commit on main since tag
v2.2.0is #221.[project].versioninpyproject.tomland themuseonclientry inuv.lockdocs/install.md, andskills/museon-content-workflow-base/SKILL.md, plus thev2.3.0Skill tree links in the install guidehtml-documents +upload,+list,folder +create, and+install-defaultsdocs/guide.md,docs/llms.txt, the bundled task index)Tests
Release
This PR does not merge itself and does not push a tag. After it is merged to
main, tag that commit and push the tag:v2.3.0must point at the merge commit (the package version on that commit is 2.3.0, and.github/workflows/release.ymlrequires the tag to be an ancestor ofmain). The workflow builds the wheel and publishes the GitHub Release. Do not tag before this PR is onmain.