Skip to content

Commit

Permalink
Revert "bump for release" (the previous version was never released)
Browse files Browse the repository at this point in the history 
This reverts commit ef55e2c.
  • Loading branch information
@exaexa
exaexa committed Jun 10, 2024
1 parent 415624b commit e79a312
Showing 1 changed file with 1 addition and 1 deletion.
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 = "JSONFBCModels"
uuid = "475c1105-d6ed-49c1-9b32-c11adca6d3e8"
authors = ["The authors of JSONFBCModels.jl"]
version = "0.1.3"
version = "0.1.2"

[deps]
AbstractFBCModels = "5a4f3dfa-1789-40f8-8221-69268c29937c"
Expand Down

2 comments on commit e79a312

@exaexa
Copy link
Member Author

@exaexa exaexa commented on e79a312 Jun 10, 2024

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

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.2 -m "<description of version>" e79a3122285ccf79516736c9558902665a090e05
git push origin v0.1.2

Please sign in to comment.