Skip to content

Commit

Permalink
Name change, major version update
Browse files Browse the repository at this point in the history 
Name changed from SynthDiag -> FusionSyntheticDiagnostics and major version number has
been rolled to 2.0.0. This will be registered with Julia Registry now.
  • Loading branch information
@anchal-physics
anchal-physics committed Oct 5, 2024
1 parent 3cb64c5 commit 4925e38
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 = "FusionSyntheticDiagnostics"
uuid = "c6e34158-aa22-49e4-bb12-15cbcb518ce6"
authors = ["Anchal Gupta <guptaa@fusion.gat.com>"]
version = "1.0.3"
version = "2.0.0"

[deps]
ArgParse = "c7e460c6-2fb9-53a9-8c5b-16f535851c63"
Expand Down

2 comments on commit 4925e38

@github-actions
Copy link

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

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 v2.0.0 -m "<description of version>" 4925e38448ebf2673c12ba298b78306d66b55332
git push origin v2.0.0

Also, note the warning: This looks like a new registration that registers version 2.0.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.