Bump JuliaRegistries/TagBot from 1 to 1.13.1

[dependabot]

Bumps JuliaRegistries/TagBot from 1 to 1.13.1.

Release notes

Sourced from JuliaRegistries/TagBot's releases.

v1.13.1

Fixed GPG tag signing. (#197)

v1.13.0

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

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/TagBot@v1.11. 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

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)