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

New release #32

Closed
dingraha opened this issue Sep 3, 2024 · 4 comments
Closed

New release #32

dingraha opened this issue Sep 3, 2024 · 4 comments

Comments

@dingraha
Copy link
Collaborator

dingraha commented Sep 3, 2024

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/114425

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.2.6 -m "<description of version>" c39af6fb764495f691d1eb57ce0c9bf99f869504
git push origin v0.2.6

@dingraha
Copy link
Collaborator Author

dingraha commented Sep 3, 2024

Arg, the TagBot workflow failed, sad. Looks like it might be an issue with the SSH deploy key, aka secrets.DOCUMENTER_KEY.

@dingraha
Copy link
Collaborator Author

@andrewning Thanks for updating the SSH key.

I tried re-running the TagBot action to get the new release tagged, but it "failed" (still a green checkmark, but no tag happened) with a No new versions to release message. I think the reason this happened is related to the value of the lookback input in the TagBot.yml file here

which tells TagBot.yml to look three days in the past to find new releases to tag. Since I reran TagBot today, aka 8 days after the release, TagBot.yml missed the release and didn't actually do anything.

I guess we could temporarily increase loopback, but I think the easiest thing to do is to just have someone with write access to byuflowlab/CCBlade.jl to run

git tag -a v0.2.6 -m "<description of version>" c39af6fb764495f691d1eb57ce0c9bf99f869504
git push origin v0.2.6

like the message above suggests (but with origin pointing to byuflowlab/CCBlade.jl not a fork).

@andrewning
Copy link
Member

ok done now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants