v1.12.8

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

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

v1.12.6

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

v1.12.5

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

v1.12.4

Yep, I broke everything. This might unbreak it.

v1.12.3

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.

v1.12.2

Fixed a CLI bug (#178).

v1.12.1

Small bugfix in changelog generation (#171).

v1.12.0

You can now set your desired release branch with the branch input if you use a weird Git setup (#170).

v1.11.1

TagBot now behaves more like you might expect when choosing the commit to tag (#169).