Skip to content

Commit

Permalink
Bump version to 0.5.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@ziotom78
ziotom78 committed Apr 17, 2020
1 parent a1630a2 commit edcb356
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 1 deletion.
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# HEAD

# Version 0.5.0

- Allow Julian Dates in `genpointings`
([45](https://github.com/lspestrip/Stripeline.jl/pull/45))
- (**Breaking change**) Drop support for Julia 1.0, 1.1, and 1.2
Expand Down
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "Stripeline"
uuid = "45029ab0-c194-11e8-0c82-65ed36a31fad"
authors = ["Maurizio Tomasi <maurizio.tomasi@unimi.it>", "Silvia Caprioli <silvia.caprioli@unimi.it>", "Federico Incardona <federico.incardona@unimi.it>"]
version = "0.4.3"
version = "0.5.0"

[deps]
AstroLib = "c7932e45-9af1-51e7-9da9-f004cd3a462b"
Expand Down

2 comments on commit edcb356

@ziotom78
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@JuliaRegistrator register

@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/13170

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.5.0 -m "<description of version>" edcb356192b0f1541e78151686240995e3e46a64
git push origin v0.5.0

Also, note the warning: This looks like a new registration that registers version 0.5.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Please sign in to comment.