0.3.6

Use Alpine 3.18 as our base image

Previously we were using Alpine 3.16. This should have no impact on anyone unless they are using this image as the base image for another.

Handle Additional GitHub secondary rate limit failure

In our previous version, we added support for retrying when a secondary rate limit failure occurred. However, since that time, we have seen secondary rate limit failures that are not handled by the previous fix. This update adds a retry for the one time we know that the limit can be triggered. If the rate limit is triggered, the bot will wait for 30 seconds before trying again. If it encounters 5 failures, it will give up and quit.

[0.3.6] - 2024-10-16

Fixed

• Handle Additional GitHub secondary rate limit failure (PR #68)

Changed

• Alpine 3.18 (PR #57)

0.3.5

Update to work with newer versions of git

Newer versions of git have added a check to see if the user running a command is the same as the user who owns the repository. If they don't match, the command fails. Adding the repository directory to a "safe list" addresses the issue.

We've updated accordingly.

Handle GitHub secondary rate limit failure

The changelog-bot-action makes extensive use of the GitHub API. As such, it can trigger rate limits that cause a failure. We've found that it is rather easy when using the bot across a number of repositories to hit a "secondary rate limit failure". Basically that is "you are doing too many API calls at once".

The error is transient. If someone was to notice, they could restart the failed changelog-bot run and it would work. However, that requires someone to notice.

With this release, we've added a retry for the one time we know that the limit can be triggered. If the rate limit is triggered, the bot will wait for 30 seconds before trying again. If it encounters 5 failures, it will give up and quit.

It is possible that we'll need to add similar returns around other GitHub API calls. If we do, additional updates will be made.

[0.3.5] - 2023-02-09

Fixed

• Update to work with newer versions of git (PR #43)

Added

• Add sleep and retry when secondary rate limit impacts on PR search (PR #46)

0.3.4

Improve logging around multiple push attempts

Previously, if the bot failed to push its updates, it would create a log message for each pull that it attempted but only for the first push. This could be confusing to the user.

Now each push and pull attempt will be logged.

Fix build error coming from PyGitHub dependency

With the release of a new version of PyGitHub, the pynacl dependency changed and no longer builds. We are fine using the previous version of PyGitHub so this update pins us to that version. If we need to upgrade in the future, we'll need to fix the "can't build pynacl" issue.

Create images on release

Permanant, unchanging images for this action are now available in DockerHub and will be updated on each release. See our examples for more details on how to use.

[0.3.4] - 2021-04-29

Fixed

• Improve logging around multiple push attempts (PR #35)
• Fix build error caused by PyGitHub version dependencies changing (PR #36)

Added

• Create images on release (PR #37)

0.3.3

Rebase on pull

Prior to this change, the changelog-bot would sometimes create a merge commit when pushing changes if it had to pull down other changes first. We now set --rebase when doing pulls to avoid muddying up the history.

[0.3.3] - 2020-09-10

Changed

• Rebase on pull (PR #33)

0.3.2

Fix broken push retries

The previous fix in 0.3.1 was incorrect. We believe this time we might have the correct fix.

[0.3.2] - 2020-08-31

Fixed

• Fix failure when attempting push retries (PR #32)

0.3.1

Fix broken push retries

Previously, we added a retry to a failed push where we would pull the latest changes and then push again. However, this didn't work as the wrong exception was being caught.

[0.3.1] - 2020-08-31

Fixed

• Fix broken push retries (PR #31)

0.3.0

[0.3.0] - 2020-08-26

Changed

• Turn on branch.autorebasesetup when pushing/pulling (PR #29)

0.2.2

[0.2.2] - 2020-08-15

Added

• Retry push on failure (PR #24)

0.2.1

[0.2.1] - 2020-06-06

Fixed

• Fix bad action.yml (PR #19)

0.2.0

[0.2.0] - 2020-05-17

Changed

• Allow for the setting of git metadata associated with commits (PR #17)