{"id":"ship:0f23a5e4-35ae-451c-9522-9b3b2f24fa70","withdrawn":false,"project":{"slug":"primer-systems-vault","name":"vault","url":"https://heyresearch.xyz/project/primer-systems-vault"},"domain":"build","claimType":"GITHUB_RELEASE","summary":"v0.4.2","sourceType":"github","sourceUrl":"https://github.com/primer-systems/vault/releases/tag/v0.4.2","publishedAt":"2026-10-02T13:46:00.000Z","detectedAt":"2026-10-02T14:14:31.534Z","precision":"EXACT","verification":"PUBLICLY_VERIFIED","countsAsBuilding":true,"countedAs":"counted","countedAsSentence":"Yes. It is one of the records HEY’s activity status is built from.","recordedAt":"2026-10-02T14:14:31.534Z","metadata":{"summary":"## 0.4.2 CI-only fix; no functional or behavioral changes from 0.4.1. ### Fixed - **`build.yml`'s release workflow was an invalid workflow file** - `secrets.BLOCKSCOUT_PRO_API_KEY` referenced directly inside a step's `if:` condition, which GitHub Actions' validator rejects (\"Unrecognized named-value: 'secrets'\"). The whole file failed to parse, so the Build Vault workflow never ran on any tagged release since the step was added - 0.4.0 and 0.4.1 shipped no desktop binaries. Moved the empty-key check into the Python step itself instead of `if:`.","releaseVersion":"v0.4.2","prerelease":false},"sources":[{"evidenceRowId":"1c0ecb49-d51e-4111-87a2-0671e5f53249","sourceType":"GITHUB_REPO","sourceUrl":"https://github.com/primer-systems/vault/releases/tag/v0.4.2","observedAt":"2026-10-02T14:14:31.534Z","metadata":{"tag":"v0.4.2","assetCount":3,"assetKinds":["desktop","other"],"prerelease":false}}],"disclaimer":"Public, source-backed activity HEY recorded. Still Building means verified activity through a tracked market drawdown — it is not a prediction, not a ranking by price, and not investment advice. Few projects meet Still Building or Under the Radar at any time; both are strict by design, and list responses carry the counts."}