Skip to content

Commit

Permalink
update news, bump version
Browse files Browse the repository at this point in the history
  • Loading branch information
@jgreener64
jgreener64 committed Jun 21, 2024
1 parent 3f6b1f6 commit 3182bf2
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 1 deletion.
8 changes: 8 additions & 0 deletions NEWS.md
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Bio3DView.jl release notes

## v1.0.0 - Jun 2024

There are no breaking changes in this release, the v1.0.0 tag is to indicate stability.

Changes:
- Drop support for Julia versions below 1.9.
- Package extensions, rather than Requires.jl, are used for BioStructures.jl and Blink.jl.

## v0.1.5 - Jul 2023

- Fix issue with rendering in VS Code.
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 = "Bio3DView"
uuid = "99c8bb3a-9d13-5280-9740-b4880ed9c598"
authors = ["Joe Greener <jgreener@hotmail.co.uk>"]
version = "0.1.5"
version = "1.0.0"

[weakdeps]
BioStructures = "de9282ab-8554-53be-b2d6-f6c222edabfc"
Expand Down

2 comments on commit 3182bf2

@jgreener64
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 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/109508

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 v1.0.0 -m "<description of version>" 3182bf2c418e32e26efbf6c72aa327ae4695f45f
git push origin v1.0.0

Please sign in to comment.