Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 4b6d126

Browse files
DilumAluthgeDilumAluthge
authoredApr 1, 2025··
Bump version from 1.0.0 to 1.1.0 (#72)
In preparation for a new release.
1 parent 848448c commit 4b6d126

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎Project.toml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
name = "SlurmClusterManager"
22
uuid = "c82cd089-7bf7-41d7-976b-6b5d413cbe0a"
33
authors = ["Joseph Kleinhenz <kleinhenz.joseph@gmail.com>"]
4-
version = "1.0.0"
4+
version = "1.1.0"
55

66
[deps]
77
Distributed = "8ba89e20-285c-5b6f-9357-94700520ee1b"

2 commit comments

Comments
 (2)

DilumAluthge commented on Apr 1, 2025

@DilumAluthge
DilumAluthge
on Apr 1, 2025
MemberAuthor

@JuliaRegistrator register

JuliaRegistrator commented on Apr 1, 2025

@JuliaRegistrator
JuliaRegistrator
on Apr 1, 2025

Registration pull request created: JuliaRegistries/General/128162

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.1.0 -m "<description of version>" 4b6d1263dc3eadd5cb759a28328a2aa7eb853856
git push origin v1.1.0
Please sign in to comment.