Repository navigation
chore(release): 0.5.1 - #38
Merged
Merged
Conversation
Bump the version in pyproject.toml and cli/constants.py and move the unreleased changelog entries (--continue, session picker, /resume, --version, doctor, resume ordering fix, test isolation) under 0.5.1.
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.
Release 0.5.1
Bumps the version to 0.5.1 in both places (
pyproject.tomlandcli/constants.py) and turns the changelog's "Unreleased" section into 0.5.1. Contents (all already merged, #37):devorch --continue/-c, a session picker for a bare--resume,/resumedevorch --version/-Vdevorch doctor(and/doctor)sessions list --herepytestrun could overwrite the real~/.devorchChecks
devorch --versionprintsdevorch 0.5.1~/.devorchuntouched by the runTo publish
v0.5.1onmain: that runs the publish workflow (PyPI upload + GitHub release) and a published version number can never be reused, so it is deliberately not part of this PRHeads-up: the open dependabot PRs #31-#34 change the actions that
publish.ymluses. Merge them after tagging, or check their CI first, so the publish workflow is not changed right before a release.