<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Package-Signing on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/package-signing/</link><description>Recent content in Package-Signing on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 04 Sep 2026 14:38:54 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/package-signing/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub CLI Linux package signing key expires September 5</title><link>https://curadevops.metacog.co.kr/insights/2026-09-04-github-cli-linux-package-signing-key-expires-september-5/</link><pubDate>Fri, 04 Sep 2026 14:38:54 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-04-github-cli-linux-package-signing-key-expires-september-5/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Act:&lt;/strong> The PGP signing key for GitHub CLI APT/RPM repos expires 2026-09-05; any managed Linux host that auto-installs or updates &lt;code>gh&lt;/code> via apt/rpm will fail package-signature verification on the first release after that date. Update the trusted keyring on those hosts today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Act:&lt;/strong> Pipelines that install &lt;code>gh&lt;/code> on Linux runners via apt or rpm will break signature verification starting with the first release after 2026-09-05; update the keyring import step in CI configs, runner setup scripts, or Dockerfiles immediately to add the new PGP key before pipelines go red.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>