Skip to content

Commit

Permalink
Lower version 0.1.4
Browse files Browse the repository at this point in the history
Downgrade version number 0.2.0 to 0.1.4, the assumed breaking release (Julia compat tightening) is non-breaking. SemVer disallows version removal, so next breaking change should be numbered v0.3.0 or v0.2.1(?).
  • Loading branch information
abhro committed Aug 6, 2024
1 parent e432a24 commit a480a44
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "AstroAngles"
uuid = "5c4adb95-c1fc-4c53-b4ea-2a94080c53d2"
authors = ["Miles Lucas <[email protected]> and contributors"]
version = "0.2.0"
version = "0.1.4"

[compat]
julia = "1.6"

2 comments on commit a480a44

@abhro
Copy link
Member Author

@abhro abhro commented on a480a44 Aug 6, 2024

Choose a reason for hiding this comment

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

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/112511

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.4 -m "<description of version>" a480a4482c3e06bef64a616c48f5b4df20ca08e2
git push origin v0.1.4

Please sign in to comment.