Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add forward-compatibility for new Beet versions #26

Merged
merged 2 commits into from
Apr 10, 2023

Conversation

Luexa
Copy link
Contributor

@Luexa Luexa commented Feb 15, 2023

This PR changes the dependency specifications for Beet and related libraries to use >= constraints instead of ^ to allow users who consume smithed-libraries as a library to use newer Beet versions. The lock format now uses the 1.3.x poetry format but the GitHub action uses 1.2.2 which is forward-compatible with this format so it should be fine. Additionally, missing run 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.

Dependencies are still locked at their current version, but library
consumers now have the flexibility to use higher `0.x` releases of
Beet and related dependencies.

Additionally `poetry.lock` uses the new format for Poetry 1.3.x, but
1.2.2 used by the GitHub Action is forwards-compatible with it so it
should be fine.
The pinned version of Mecha seems to allow `run` to be omitted, but in
new versions of Mecha this is not allowed and causes `beet build` to
fail. Now the build should work with newer versions of Mecha.
@RitikShah
Copy link
Collaborator

Thanks for this! I think I try to use >= but poetry add <package>@latest sometimes messes with it!

@RitikShah
Copy link
Collaborator

Hmm, i'm not sure what u mean that run needs to be included, the latest versions of bolt allows for implicit runs?

@Luexa
Copy link
Contributor Author

Luexa commented Feb 15, 2023 via email

@vberlier
Copy link

The latest command tree includes execute summon which means that to access the normal summon command behind execute you now need to use run explicitly.

@RitikShah
Copy link
Collaborator

The latest command tree includes execute summon which means that to access the normal summon command behind execute you now need to use run explicitly.

ahh, this makes a ton of sense 🤔

@RitikShah RitikShah merged commit 85ea724 into Smithed-MC:main Apr 10, 2023
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants