Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add package release in Julia #85

Closed
ricboer0 opened this issue Nov 12, 2024 · 14 comments · Fixed by #88
Closed

Add package release in Julia #85

ricboer0 opened this issue Nov 12, 2024 · 14 comments · Fixed by #88
Assignees
Labels
enhancement New feature or request size: 5

Comments

@ricboer0
Copy link
Collaborator

No description provided.

@ricboer0 ricboer0 added enhancement New feature or request size: 5 labels Nov 12, 2024
@ricboer0 ricboer0 added this to the Sprint_10-12_2024 milestone Nov 12, 2024
@ricboer0 ricboer0 self-assigned this Nov 12, 2024
@ricboer0 ricboer0 moved this to Todo in prismAId Nov 12, 2024
@ricboer0 ricboer0 moved this from Todo to In Progress in prismAId Nov 15, 2024
@ricboer0 ricboer0 linked a pull request Nov 15, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress to Done in prismAId Nov 15, 2024
@ricboer0 ricboer0 reopened this Nov 15, 2024
@ricboer0 ricboer0 moved this from Done to In Progress in prismAId Nov 15, 2024
@open-and-sustainable open-and-sustainable deleted a comment from github-actions bot Nov 19, 2024
Copy link

@JuliaRegistrator register subdir=julia/PRISMAID branch=85-add-package-release-in-julia registry=https://github.com/open-and-sustainable/julia

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/119750

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 PRISMAID-v0.6.3 -m "<description of version>" c8b551eb97647035ac772b6a68db46a07f223f11
git push origin PRISMAID-v0.6.3

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

@ricboer0
Copy link
Collaborator Author

@JuliaRegistrator register subdir=julia/PRISMAID

@github-project-automation github-project-automation bot moved this from In Progress to Done in prismAId Nov 20, 2024
@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/119806

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 PRISMAID-v0.6.3 -m "<description of version>" b3af9ae48b321393ad32f82f885ae924870c65ce
git push origin PRISMAID-v0.6.3

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

@ricboer0
Copy link
Collaborator Author

@JuliaRegistrator register subdir=julia/PrismAIdConnect

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/119811

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 PrismAIdConnect-v0.6.3 -m "<description of version>" d42d14ab0f46adf35db98eca94650c0f61da521c
git push origin PrismAIdConnect-v0.6.3

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

@ricboer0
Copy link
Collaborator Author

@JuliaRegistrator register subdir=julia/PrismAId

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/119817

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 PrismAId-v0.6.3 -m "<description of version>" c69edeb6ab62eec8015e0fb0769df7d48650cbbd
git push origin PrismAId-v0.6.3

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

@ricboer0
Copy link
Collaborator Author

@JuliaRegistrator register subdir=julia/PrismAId

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/120053

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 PrismAId-v0.6.4 -m "<description of version>" e3ac3c240ac2d8a1f3c7558a408b04072039c4fb
git push origin PrismAId-v0.6.4

@ricboer0
Copy link
Collaborator Author

@JuliaRegistrator register subdir=julia/PrismAId

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/122880

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 PrismAId-v0.6.5 -m "<description of version>" aeb8770fad8e075f682aa9fb61a536412e8156af
git push origin PrismAId-v0.6.5

@ricboer0
Copy link
Collaborator Author

@JuliaRegistrator register subdir=julia/PrismAId

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/123258

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 PrismAId-v0.6.6 -m "<description of version>" 80d2fc4b03150c54171ccf7c4746db0d6f22e215
git push origin PrismAId-v0.6.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request size: 5
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants