Repository navigation
release: 0.6.1 - #331
Merged
Merged
release: 0.6.1#331
Conversation
Ships the #329 fix: an annotation that announces a success is no longer handed back as somewhere to start. The Action pins patchrail >=0.6.0,<0.7.0 and surfaces runner_errors as PR annotations, so its users pick this up on the next run without changing anything.
The version-consistency test guards that the quickstart advertises the version that actually ships; it caught the bump leaving the README behind.
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.
Patch release for #329 (merged in #330).
The Action pins
patchrail>=0.6.0,<0.7.0and surfacesrunner_errorsas PR annotations, so until this is on PyPI its users still get pointed at✅ Autofix task started.as somewhere to start. Publishing closes that loop with no change on their side.pyproject.toml,__init__.py, anduv.lock(kept in step —uv lock --checkis a CI gate as of chore: sync uv.lock with 0.3.1 and gate lockfile drift in CI #313).