chore: use images.lock.json as version provenance #165
No reviewers
Labels
No labels
prio/P1
prio/P2
prio/P3
status/leftover
status/new
status/parked
type/feature
type/ops
type/research
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MeshFlowsGPL/meshflows!165
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/remove-versions-manifest"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
versions.yamlpackage manifest.images.lock.jsonthe source for per-service immutable image provenance.publish-product-version.ymlrecovery retagging to readimages.lock.json.source_tagoverride for recovery when no lockfile artifact is available.Validation
git diff --checkpasses.versions.yamlreferences remain.Note
The normal VERSION-change-on-main build policy still forces a full build today. This PR removes the obsolete manifest and fixes the no-rebuild/product-retag source path; changing the automatic full-build policy should be a separate, reviewed workflow change.