v0.1.3
[0.1.3] — 2026-05-04
Re-tag of v0.1.2's tree to refresh distribution channels. No source
changes — the binary content is identical to v0.1.2.
Why
A consumer reported go install github.com/RandomCodeSpace/docsiq@v0.1.2
failing in their local environment while v0.1.0 worked. The v0.1.2 tag,
GitHub release, proxy.golang.org cache, and sum.golang.org checksum
DB are all healthy and signed; the failure was downstream of those. This
release is published primarily to give the affected install a fresh tag
to retry against.
Reference
- Upstream commit:
afdacc5639d3(same as v0.1.2) - Functionality identical to v0.1.2 — see v0.1.2 notes
for the per-phase upload progress feedback that landed there.
Upgrade impact
Drop-in. No code changes; refresh of signed binaries and re-publication
through the release pipeline only.
Verify
All artifacts are signed with cosign keyless via Sigstore.
cosign verify-blob \
--certificate-identity-regexp 'https://github.com/RandomCodeSpace/docsiq/\.github/workflows/release\.yml.*' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--certificate docsiq-v0.1.3-linux-amd64.pem \
--signature docsiq-v0.1.3-linux-amd64.sig \
docsiq-v0.1.3-linux-amd64