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

Revert back to standard dependency version requirements #9

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

kohlerj
Copy link
Contributor

@kohlerj kohlerj commented Jan 13, 2025

Rewrote the poetry version requirement

Using the caret ^ for versioning means that the plugins requires poetry >=2.0.0,<3.0.0. This means that one cannot simply upgrade the plugin then update poetry when coming from poetry 1.8.3.

The plugin needs to be removed and reinstalled once poetry is updated.

This correction makes it easier. Upgrade the plugin poetry self add poetry-pre-...@latest and then update poetry poetry self update

It also does not break the compatibility continuity of the plugin.

Using the caret ^ for versioning means that the plugins requires poetry >=2.0.0,<3.0.0. This means that one cannot simply just upgrade the plugin then update poetry when coming from poetry 1.8.3. The plugin needs to be removed and reinstalled once poetry is updated. This version makes it easier. Upgrade the plugin poetry `self add poetry-pre-...@latest`

It also does not break the compatibility continuity of the plugin.
@kohlerj
Copy link
Contributor Author

kohlerj commented Jan 13, 2025

You might need to delete the 0.2.0 you release. I am probably the only one who downloaded it.

@vstrimaitis vstrimaitis merged commit e3029cf into vstrimaitis:master Jan 13, 2025
@vstrimaitis
Copy link
Owner

Alright, I published 0.2.1 - give it a go!

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.

2 participants