Skip to content

Commit

Permalink
Bumped to 0.1.16
Browse files Browse the repository at this point in the history
  • Loading branch information
brainandforce committed Nov 16, 2023
1 parent 5a17160 commit 5ed11b3
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [0.1.16]: 2023-11-16

### Added
- `[compat]` bounds are now provided for testing dependencies (Aqua.jl, Test.jl, TOML.jl).
- New `Multiplicity{M}` type for valid spin values associated with multiplicity `M`.
Expand Down Expand Up @@ -182,6 +184,7 @@ provided `oneunit(T)` is defined.
Initial release of Electrum.jl

[Unreleased]: https://github.com/brainandforce/Electrum.jl
[0.1.16]: https://github.com/brainandforce/Electrum.jl/releases/tag/v0.1.16
[0.1.15]: https://github.com/brainandforce/Electrum.jl/releases/tag/v0.1.15
[0.1.14]: https://github.com/brainandforce/Electrum.jl/releases/tag/v0.1.14
[0.1.13]: https://github.com/brainandforce/Electrum.jl/releases/tag/v0.1.13
Expand Down
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ authors = [
"Amber Lim <[email protected]>",
"Patrick Cross <[email protected]>"
]
version = "0.1.16-dev"
version = "0.1.16"

[deps]
ComputedFieldTypes = "459fdd68-db75-56b8-8c15-d717a790f88e"
Expand Down

2 comments on commit 5ed11b3

@brainandforce
Copy link
Owner Author

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/95463

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.16 -m "<description of version>" 5ed11b3baf32ec7efb26057eb5fe489e2fbcbce1
git push origin v0.1.16

Please sign in to comment.