sigit-code 1.5.3__tar.gz → 1.5.4__tar.gz

{sigit_code-1.5.3 → sigit_code-1.5.4}/.github/workflows/release-github.yml

@@ -141,8 +141,41 @@ jobs:
           export PKG_VERSION="${RELEASE_VERSION}"
           export PKG_BINARY="./release/${PROJECT_NAME}-${{ matrix.name }}"
 
-          /tmp/nfpm package --config packaging/nfpm.yaml --packager deb --target ./release/
-          /tmp/nfpm package --config packaging/nfpm.yaml --packager rpm --target ./release/
+          # An empty version is worse than a hard failure here: nfpm accepts it
+          # and silently emits a "0.0.0~rc0" package that would be attached to
+          # the release. Same for a missing binary, which only surfaces as an
+          # opaque glob error. Fail loudly instead.
+          if [ -z "${PKG_VERSION}" ]; then
+            echo "RELEASE_VERSION is empty; refusing to build packages" >&2
+            exit 1
+          fi
+          if [ ! -f "${PKG_BINARY}" ]; then
+            echo "Staged binary ${PKG_BINARY} not found" >&2
+            exit 1
+          fi
+
+          # nfpm expands ${VAR} in most fields but NOT in contents.src, so the
+          # config is rendered up front and nfpm only ever sees literal values.
+          # envsubst comes from gettext-base, preinstalled on the Ubuntu runner
+          # images. The explicit variable list keeps it from clobbering any
+          # other shell-looking text added to the config later.
+          if ! command -v envsubst >/dev/null 2>&1; then
+            sudo apt-get update && sudo apt-get install -y gettext-base
+          fi
+
+          envsubst '${PKG_ARCH} ${PKG_VERSION} ${PKG_BINARY}' \
+            < packaging/nfpm.yaml > /tmp/nfpm.rendered.yaml
+
+          /tmp/nfpm package --config /tmp/nfpm.rendered.yaml --packager deb --target ./release/
+          /tmp/nfpm package --config /tmp/nfpm.rendered.yaml --packager rpm --target ./release/
+
+          # Guard against a packager silently producing nothing.
+          for ext in deb rpm; do
+            if ! compgen -G "./release/*.${ext}" >/dev/null; then
+              echo "No .${ext} produced" >&2
+              exit 1
+            fi
+          done
 
           ls -la ./release/
 

{sigit_code-1.5.3 → sigit_code-1.5.4}/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 1.5.4
+
+- **CI**: nfpm config expanded to include package version and binary path
+
 ## 1.5.3
 
 Adds browser-based sign-in, expands distribution channels to Windows (winget,

{sigit_code-1.5.3 → sigit_code-1.5.4}/Cargo.lock

@@ -5778,7 +5778,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba"
 
 [[package]]
 name = "sigit"
-version = "1.5.3"
+version = "1.5.4"
 dependencies = [
  "agent-client-protocol",
  "anyhow",

{sigit_code-1.5.3 → sigit_code-1.5.4}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "sigit"
-version = "1.5.3"
+version = "1.5.4"
 edition = "2024"
 description = "siGit Code — ACP-compatible AI coding agent. Sí, git."
 documentation = "https://github.com/getsigit/sigit"

{sigit_code-1.5.3 → sigit_code-1.5.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sigit-code
-Version: 1.5.3
+Version: 1.5.4
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers

{sigit_code-1.5.3 → sigit_code-1.5.4}/packaging/nfpm.yaml

@@ -7,7 +7,9 @@
 # config.
 #
 # PKG_ARCH and PKG_VERSION are set by release-github.yml; PKG_BINARY points at
-# the renamed binary already staged in release/.
+# the renamed binary already staged in release/. nfpm does not expand env vars
+# in contents.src, so release-github.yml renders this file with envsubst before
+# invoking nfpm.
 name: sigit
 arch: ${PKG_ARCH}
 platform: linux