dfdx / Umlaut.jl

The Code Tracer

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Register Umlaut

dfdx opened this issue · comments

Registration pull request created: JuliaRegistries/General/63924

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.5 -m "<description of version>" 5b9e52c359dd16fc3cee3b3e20bc3830de96d158
git push origin v0.2.5

Registration pull request created: JuliaRegistries/General/64356

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

Registration pull request created: JuliaRegistries/General/65586

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

Registration pull request created: JuliaRegistries/General/65740

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.4.1 -m "<description of version>" 2011aeeb07004e1c269395d00a7bfb6e6bb65362
git push origin v0.4.1

Registration pull request created: JuliaRegistries/General/65861

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.4.2 -m "<description of version>" 755812e9303420a1b4e28428758b9ae1686475b6
git push origin v0.4.2

Registration pull request created: JuliaRegistries/General/66691

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.4.3 -m "<description of version>" 447eec4efe0895ca7e401bd0ed962ea9ddccbbda
git push origin v0.4.3

Registration pull request created: JuliaRegistries/General/66969

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.4.4 -m "<description of version>" 9b139d7d88bca199830ae797373931c439c47abd
git push origin v0.4.4

Registration pull request created: JuliaRegistries/General/67199

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

Registration pull request created: JuliaRegistries/General/68943

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.4.6 -m "<description of version>" 34750896fc22929ef01a1c60ef4bb91599468f68
git push origin v0.4.6

Registration pull request created: JuliaRegistries/General/69409

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

Registration pull request created: JuliaRegistries/General/71313

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.4.8 -m "<description of version>" 3a17c22e77893c712683156335e57fe658c8fcea
git push origin v0.4.8

Registration pull request created: JuliaRegistries/General/74555

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

Registration pull request created: JuliaRegistries/General/79440

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

@dfdx could we please make a release? Not sure if I have permission to do it / if you have some reason for holding off making a release

Ok, the bot seems to be down. Let's wait a couple of hours before trying out other ways.

Is there a reason that tagbot is being used from this issue, rather than as comments on commits, as is done in other repos?

Hmm, I only know how to use Registrator.jl which suggests to have a comment in an issue. Can you show me an example of a repo that triggers a new release via comments on commits?

I also use registrator. It looks like you can either comment in an issue, or comment directly on commits -- see here . We tend to do the latter in the JuliaGPs ecosystem, e.g. in AbstractGPs.jl.

Doesn't seem to work either, although I'm not sure I did it right.

Anyway, I did it the old way via JuliaHub and it worked.

@dfdx doesn't look like I'm able to register the patch version. Any chance you could make a release?

I've just created the registration PR via the web interface since the integration with JuliaRegistrator seems to be broken:

JuliaRegistries/General#88596

Ahh okay, cool. If you would be happy to give me developer rights on this repo, I would be happy to take a look at the registrator integration issues.

It would be great! I've sent you an invitation to the repo.

Hmmm annoyingly it doesn't look like I'm able to play around with the registrator installation on Umlaut because I don't own the repo. I guess we continue to use the web interface

Registration pull request created: JuliaRegistries/General/88746

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.5.3 -m "<description of version>" 6562655de4484223ddf61d9bf152858b18218759
git push origin v0.5.3

Oh, I re-activated it! 🎉

Registration pull request created: JuliaRegistries/General/88812

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

Registration pull request created: JuliaRegistries/General/89355

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.5.5 -m "<description of version>" 21a3affb606b3ec75176b65792d1046a218c53ae
git push origin v0.5.5

Registration pull request created: JuliaRegistries/General/90043

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

Registration pull request created: JuliaRegistries/General/93680

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.5.8 -m "<description of version>" 8034b977ee761c56d1c6043ae82af372cdad52b3
git push origin v0.5.8

Also, note the warning: Version 0.5.8 skips over 0.5.7
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.

Registration pull request created: JuliaRegistries/General/93681

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.5.7 -m "<description of version>" 0fa010b23109ec90773dfda8b01782f8b060d7b8
git push origin v0.5.7

Registration pull request updated: JuliaRegistries/General/93680

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.5.8 -m "<description of version>" 1fdef90fd47c07874828d2306d97254966115858
git push origin v0.5.8

@dfdx what was the reason that you blocked the release of the new version by commenting on the PR to the general registry? Is there something that requires fixing?

Huh! It's a bug! I left this comment 3 weeks ago when I mistakenly bumped version to 0.5.8, tried to register and got a message that I skipped version 0.5.7. I then resubmitted PR with version 0.5.7, but this PR with 0.5.8 haven't been neither closed, not merged. Now, when I invoked Registrator again, it linked the old PR.

Let me think how to overcome it now 🤔

Ahh okay. I think the PR says how to unblock:

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

Registration pull request created: JuliaRegistries/General/95173

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

@willtebbutt Neither posting a noblock comment, nor registering via JuliaHub worked, but I was able to register it with tag v0.6.0.

Registration pull request created: JuliaRegistries/General/95673

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.6.1 -m "<description of version>" 0263cdf8cf14aa842926a3583058e4681448f15c
git push origin v0.6.1

Registration pull request created: JuliaRegistries/General/96241

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

Registration pull request created: JuliaRegistries/General/100837

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

Registration pull request created: JuliaRegistries/General/103326

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.7.0 -m "<description of version>" 9b0d4fbe907e46ead0e7973c1a7f6b441f35f902
git push origin v0.7.0