Releases: JuliaRegistries/TagBot
v1.7.2
Another bugfix... Today is not a good day. Sorry to everyone's email inboxes.
v1.7.1
Bugfix for the lookback thing default value.
v1.7.0
TagBot will no longer clone your repository unless there are new releases to make, which will help keep your traffic graphs accurate.
A side effect of this is that the amount to look back in time for new releases can no longer be automatically calculated. Instead, there's the new lookback
input. Chances are, you don't need to use it unless you're running TagBot less than once every three days.
v1.6.1
Fixes a bug with some PRs or issues not appearing in the changelog if they were closed by the last commit.
v1.6.0
Some minor new features:
- The lookback period for new releases is now calculated by checking the time between TagBot runs and multiplying it by 3. If you run TagBot once a week, then it'll look back three weeks for new versions. The minimum period is the old hardcoded value: 3 days.
- The
changelog_ignore
input has been added to specify labels whose issues should be ignored by the changelog generator, and some additional defaults have been added. Also, this filtering happens in the code rather than in the default template, so custom changelog templates now get this for free. - The
dispatch_delay
input has been added to specify how many minutes to wait after creating a repository dispatch event. The default is its old hardcoded value: 5 minutes.
v1.5.4
This should fix a strange issue that occurred when TagBot was handling your first package release.
v1.5.3
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
You can now use SSH keys that have passwords and GPG keys that have passwords!
v1.5.1
Oops, I broke SSH keys by not including the ssh
executable in the new Docker image.
v1.5.0
GPG support has been brought back, you can supply your own private key and get signed tags!