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

Use Mau v 2.x #14

Merged
merged 4 commits into from
Oct 20, 2021
Merged

Use Mau v 2.x #14

merged 4 commits into from
Oct 20, 2021

Conversation

lgiordani
Copy link
Collaborator

This uses the new API of Mau 2.x and ensures that version is installed through the requirements

@lgiordani lgiordani requested a review from justinmayer October 18, 2021 21:33
Copy link
Contributor

@justinmayer justinmayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ciao! Other than reverting the version number change in pyproject.toml (which happens automatically and doesn't need to be manually incremented), this looks good to me.

pyproject.toml Outdated
@@ -1,6 +1,6 @@
[tool.poetry]
name = "pelican-mau-reader"
version = "1.0.2"
version = "2.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change to this line should be reverted. The version number will be automatically incremented by AutoPub, based on the value specified in the Release type: field. Since in this case that value is specified as major, the version number will be automatically incremented from 1.0.x to 2.0.0 when AutoPub processes the RELEASE.md file.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, I don't really know why I did it 🤦

@@ -31,7 +31,7 @@ classifiers = [
python = ">=3.6.2,<4.0"
pelican = ">=4.5"
markdown = {version = ">=3.2", optional = true}
mau = ">=1.4.0,<2.0"
mau = ">=2.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congrats on removing the upper bound. More and more, I get the feeling that upper bounds on version specifiers may well be an anti-pattern. 👍

@lgiordani lgiordani requested a review from justinmayer October 19, 2021 16:16
@lgiordani lgiordani merged commit f3b33f5 into main Oct 20, 2021
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