Add forward-compatibility for new Beet versions #26
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.
This PR changes the dependency specifications for Beet and related libraries to use
>=
constraints instead of^
to allow users who consumesmithed-libraries
as a library to use newer Beet versions. The lock format now uses the1.3.x
poetry format but the GitHub action uses1.2.2
which is forward-compatible with this format so it should be fine. Additionally, missingrun
subcommands have been added to a couple functions to avoid errors with the current Mecha version.Note that this PR does not update Beet, Mecha, etc. so GitHub actions should generate the same result as before. A new version is probably necessary for PyPI, but idk how to handle that.