gh (2.46.0-3)
[PTS] [DDPO]
COMMITS: VCS has seen 2 commits since the debian/2.46.0-3 tag
- Git: https://salsa.debian.org/go-team/packages/gh.git
-
- Branch: debian/sid
- Path: debian/changelog
- Repo size: 5386240
- Browser: https://salsa.debian.org/go-team/packages/gh
- Last scan: 2025-02-10 12:39:12+00
- Next scan: 2025-02-17 02:55:00+00
- Merge requests: 1
- CI pipeline status: success
- Debian changelog in Git:
gh (2.46.0-3) unstable; urgency=medium
[ Loren M. Lang ]
* Apply patch to fix CVE-2024-54132 (Closes: #1089120)
* Apply patch to fix CVE-2024-53858 (Closes: #1088808)
* Don't let $GH_TOKEN from the build environment break the test
* Fixed a build error introduced in a recent test change
* Fixed an issue with flaky download tests
* Enabled Salsa CI for packaging repository for improved quality
assurance before uploads to Debian archives
[ Otto Kekäläinen ]
* Update copyright and uploaders metadata to match current maintainers
-- Otto Kekäläinen <otto@debian.org> Sun, 12 Jan 2025 21:43:14 -0800
- This branch is 2 commits ahead of tag debian/2.46.0-3
- Git log:
commit f42f34ae1ad2f35f239453f940ed343b30358025
Author: Otto Kekäläinen <otto@debian.org>
Date: Mon Jan 13 19:54:47 2025 -0800
Stop polluting upstream file paths and put build artifacts in debian/build
commit 0861af5eb85356d67cf7e0ba7de011b93c3439ed
Author: Otto Kekäläinen <otto@debian.org>
Date: Mon Jan 13 19:52:14 2025 -0800
Add minimal gbp.conf so that it is explicit what settings this repo has
The repository was already using pristine-tar, so include it in the
configuration to next upstream import does not accidentally omit it.
Also configure the upstream tag format and enforce that the Debian
maintainer signs tags.
This is not yet the ideal gbp.conf, just the bare minimum for next
upstream import to be consistent. Branches should be switched to DEP-14
later when the Go team rolls out workflow updates.