Repository navigation
release: align artifact-record lineage with M1 trackers #267
Description
Activity
🔗 Related PRs
#206 - ci: move job transfers to Blacksmith storage [merged]
#208 - ci: minimize Blacksmith cache storage [merged]
#247 - feat(iac): validate static deployment targets [merged]
#251 - feat(iac): render portable GraphForge deployment specs [merged]
#258 - chore(release): prepare v0.5.0 publication [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
- added a commit that references this issue
on Jul 31, 2026
Summary
The final v0.5.0 release-record generator emits the correct version, tag, commit SHA, checksum, license, and explicit SBOM/provenance disposition, but its issue lineage still points to retired legacy trackers (
#2783,#2793,#2794,#2799, and#742). The accompanying artifact-record guide and clean-environment script header carry the same stale release model.That output is not acceptable evidence for the current M1 release close in #192.
Scope
Acceptance criteria
graphforge-release-record-v1output contains no retired tracker IDs.clean-env-verify.pyand has a recorded SHA-256 checksum.Blocks #192.