Upstream tag: v1.111.0
Upstream commit: 05d11558
Release monitoring project: 6804
Resolves: rhbz#2269599

If you need to do any change in this pull request, you can clone Packit's fork and push directly to the source branch of this PR (provided you have commit access to this repository):

git clone ssh://$YOUR_USER@pkgs.fedoraproject.org/forks/packit/rpms/golang-github-digitalocean-godo.git
cd golang-github-digitalocean-godo
git checkout 1.111.0-rawhide-update-pull_from_upstream
git push origin 1.111.0-rawhide-update-pull_from_upstream

Alternatively, if you already have the package repository cloned, you can just fetch the Packit's fork:

cd golang-github-digitalocean-godo
git remote add packit ssh://$YOUR_USER@pkgs.fedoraproject.org/forks/packit/rpms/golang-github-digitalocean-godo.git
git fetch packit refs/heads/1.111.0-rawhide-update-pull_from_upstream
git checkout 1.111.0-rawhide-update-pull_from_upstream
git push packit 1.111.0-rawhide-update-pull_from_upstream

If you have the koji_build job configured as well, make sure to configure the allowed_pr_authors and/or allowed_committers (see the docs) since by default, Packit reacts only to its own PRs.

Before pushing builds/updates, please remember to check the new version against the packaging guidelines.

For example, please:

• check that the new sources only contain permissible content
• check that the license of the new version has not changed
• check for any API/ABI and other changes that may break dependent packages
• check the autogenerated changelog

:exclamation: Changed default for the changelog entry generated by Packit

We would like to bring to your attention a recent update regarding the default changelog entry generated by Packit during release syncing. Going forward, the default changelog entry will be generated as follows:

- Update to version {version}

followed by a Bugzilla reference if thereis an open bug about a new upstream release.
This aligns with the Fedora Packaging Guidelines and has been agreed upon in this discussion. If you prefer a different behaviour, you can override this default in your configuration, e.g. by using custom command(s) in changelog-entry action (see example).