Repository navigation
v0.3.2
Fixed
-
--versionsays which release the binary came from, and says it the
same way however it was installed. Two bugs, one line:
go install …@latestapplies no ldflags, so an installed binary called
itselfdev (unknown, built unknown, …)and could not name the release
at all; and goreleaser stamps its{{.Version}}with the leadingv
stripped, so an archive said0.3.1where the module version says
v0.3.1. The same release therefore reported two different strings
depending on how somebody installed it, and anything parsing
--versiongot a different answer per install method.The linker stays the source of truth for a release build; the module
version out ofdebug.BuildInfois the fallback, which is the honest
answer when nothing stamped anything. Both spellings normalise to the
one the tag, the module version and the release all use. The four
sibling servers fixed this after an outside reader compared them side
by side; this one had not. -
syft is pinned to v1.51.1 in the release workflow, which is what the
four sibling servers pin. The action was pinned by SHA and the tool it
installs was not — the same hole that failed v0.3.0 through cosign, one
step below it in the same job. syft writes the SBOM attached to every
archive, so an unpinned one changes what a release ships, or fails it,
without anything in this repository moving.
Added
-
The
pinsgate classifies every action, and an unknown one fails it.
The gate could only ever check the versions that were written; an
action that installs a tool and names no version at all is an absence,
which is how both the cosign and the syft holes sat there unreported.
Every action is now in one of two tables — the installers, with the
input that pins the tool each one installs, or the actions that install
nothing, each with the reason — and an action in neither fails the
gate, because being unclassified is the state that let the first two
through.Watched failing on all three shapes before being trusted:
cosign-release
removed,syft-versionremoved, and an unclassified installer added.
Verify a binary signature:
cosign verify-blob \
--certificate pipedrive-mcp-0.3.2-linux-amd64.tar.gz.cert \
--signature pipedrive-mcp-0.3.2-linux-amd64.tar.gz.sig \
--certificate-identity-regexp 'https://github.com/mmedum/pipedrive-mcp/.+' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
pipedrive-mcp-0.3.2-linux-amd64.tar.gzVerify the SLSA build-provenance attestation:
gh attestation verify pipedrive-mcp-0.3.2-linux-amd64.tar.gz --owner mmedum