vcswatch reports that
this package seems to have a new changelog entry (version
1.2.2-2, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 30953b256349b0ee5bfef8f885d4522e4f6622e0
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date: Tue Nov 10 02:44:53 2026 +0100
d/control: Build-Depends on what the go.work workaround uses
commit 712338fd6032f85ed0961b59d1b47d3a81f810f1
Author: Simon Quigley <tsimonq2@debian.org>
Date: Mon Nov 9 17:50:08 2026 -0600
Upload to unstable
commit f3f1e82942a0622cad15c9ff9f3828008abace4a
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date: Tue Nov 3 02:03:42 2026 +0100
d/changelog: close the ITP
commit 88b8c0453627753066805e3c08c2e3a66d40a9e5
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date: Mon Nov 2 23:45:10 2026 +0100
d/changelog: initial release
commit 4956cfa7a10af0c6d56013a73908bd1f1050e169
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date: Mon Nov 2 23:45:08 2026 +0100
d/copyright: declare the DCO file
commit 0718ca309e6547c775c31f35a9d98e5a3d328c99
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date: Mon Nov 2 23:45:06 2026 +0100
d/rules: write go.work before dh_auto_build so autopkgtest gets the fixes
autopkgtest overrides dh_auto_configure, so dh-go only wrote go.work inside
dh_auto_build and fix-go-work never ran there.
commit 18005a5c0d97faf614f55fd39884a7bbc64c0e78
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date: Fri Oct 30 15:28:50 2026 +0100
Initial packaging
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/golang-github-fluxcd-cli-utils.png){kind=link}