Skip to content

Releases: JuliaRegistries/TagBot

v1.14.1

04 Oct 13:10
4dfecaa
Compare
Choose a tag to compare

The label "skip changelog" can now be used on issues and PRs to exclude them from the changelog. (#213)

v1.14.0

13 Aug 13:58
d04aea4
Compare
Choose a tag to compare

You can now tell TagBot to create draft releases instead of full Git tag + GitHub releases. (#207)

v1.13.1

01 Apr 19:41
e09d435
Compare
Choose a tag to compare

Fixed GPG tag signing. (#197)

v1.13.0

25 Mar 22:22
9d7c2f9
Compare
Choose a tag to compare

This release brings much better support for accessing private registries via a read-only deploy key. See custom registries for more details.

v1.12.8

01 Dec 23:15
bd43768
Compare
Choose a tag to compare

Nothing that affects users in this release, except for some behind-the-scenes action:

Old versions of TagBot have been corrected to run the corresponding TagBot Docker image, and 1.MINOR tags now exist for all 1.x versions. That means that if you wanted to stay on TagBot 1.11.x for whatever reason, you could now do so by using JuliaRegistries/[email protected]. Previously, any 1.MINOR.PATCH version would just get you the latest 1.x Docker image. This shouldn't change anything for the vast majority of users, and I don't recommend nor support old versions, but they're available to you now.

v1.12.7

26 Nov 17:04
v1.12.7
4c4833d
Compare
Choose a tag to compare

A warning is now printed if you're running TagBot as a cron job. Please update your workflows as described here!

v1.12.6

23 Nov 23:08
v1.12.6
035a60b
Compare
Choose a tag to compare

Key decoding was mostly fixed last time, and now it should be completely fixed! (#182)

v1.12.5

07 Nov 17:40
v1.12.5
7ae4a0e
Compare
Choose a tag to compare

KEY DECODING IS (probably) FIXED!!! (#180)

v1.12.4

04 Nov 17:07
v1.12.4
c4e6c6a
Compare
Choose a tag to compare

Yep, I broke everything. This might unbreak it.

v1.12.3

04 Nov 16:53
v1.12.3
8c8f966
Compare
Choose a tag to compare

You can now add inputs to your workflow_dispatch trigger. You can use this feature to override certain config options for just a single manual TagBot run. For example, perhaps you've just installed TagBot on a package repo with a couple of versions that were registered a week ago, and those versions do not yet have Git tags/GitHub releases. TagBot will not fill in those releases for you, because they are older than the default lookback.

You could edit your TagBot.yml like so:

name: TagBot
on:
  issue_comment: # ...
  workflow_dispatch:
    inputs:  # NEW!
      lookback:
jobs: # ...

Then, when you trigger a manual TagBot run, you can enter the value 14 for lookback which will override the default and cause TagBot to look for new versions registered within the last two weeks.

You can override any input in the same manner.


Alternatively, this might just break everything. Fingers crossed.