Skip to content

Releases: JuliaRegistries/TagBot

v1.5.4

10 Feb 02:13
v1.5.4
a693213
Compare
Choose a tag to compare

This should fix a strange issue that occurred when TagBot was handling your first package release.

v1.5.3

09 Feb 02:14
v1.5.3
c4c3712
Compare
Choose a tag to compare

If your repository does not have a Project.toml or JuliaProject.toml, TagBot now exits without an error.
You should remove TagBot if you do not have any plans to register your repository.

v1.5.2

07 Feb 00:45
v1.5.2
264a284
Compare
Choose a tag to compare

You can now use SSH keys that have passwords and GPG keys that have passwords!

v1.5.1

06 Feb 01:18
v1.5.1
d54f8b4
Compare
Choose a tag to compare

Oops, I broke SSH keys by not including the ssh executable in the new Docker image.

v1.5.0

05 Feb 12:30
v1.5.0
d6ee9c5
Compare
Choose a tag to compare

GPG support has been brought back, you can supply your own private key and get signed tags!

v1.4.4

28 Jan 05:21
v1.4.4
8b71137
Compare
Choose a tag to compare

When using SSH keys, host key verification is performed by first importing GitHub's key (instead of disabling the check).

v1.4.3

17 Jan 14:29
v1.4.3
a0895ac
Compare
Choose a tag to compare

You can now use Base64-encoded SSH keys, so if you have such a key as a repo secret for Documenter, you can reuse that one. Hopefully the last SSH-key-related release.
Also, a small logging bug was fixed.

v1.4.2

17 Jan 06:22
v1.4.2
cd7b198
Compare
Choose a tag to compare

Another bugfix for SSH keys. Hopefully the last one!

v1.4.1

17 Jan 02:03
v1.4.1
fb32cd0
Compare
Choose a tag to compare

Bugfix for the SSH key feature (I am 99% sure that this will work now).

v1.4.0

16 Jan 03:39
v1.4.0
517743e
Compare
Choose a tag to compare

This release adds the ability to provide an SSH key to use for creating tags, which works around some limitations with the default token. See the "Personal Access Tokens" and "SSH Deploy Keys" README sections, issue #47 and PR #49 for more details.