Currently, image-info.json is published by committing directly to the dotnet/versions repo. Branch protection or rulesets can prevent pushes to the repo, leaving automation dependent on stale image-info and causing unnecessary re-builds.
ImageBuilder should create the image-info artifact when the final image set is produced during the Post-Build stage of the build pipeline, then push/copy it to the registry as part of the same Publish flow as the images. A successful image publish should include both the images and matching image-info artifact.
For .NET itself, the OCI artifact should remain private until we decide on a public name and destination. Syncing image-info back to dotnet/versions should be handled separately by a scheduled pipeline that opens automated pull requests.
Currently, image-info.json is published by committing directly to the dotnet/versions repo. Branch protection or rulesets can prevent pushes to the repo, leaving automation dependent on stale image-info and causing unnecessary re-builds.
ImageBuilder should create the image-info artifact when the final image set is produced during the Post-Build stage of the build pipeline, then push/copy it to the registry as part of the same Publish flow as the images. A successful image publish should include both the images and matching image-info artifact.
For .NET itself, the OCI artifact should remain private until we decide on a public name and destination. Syncing image-info back to
dotnet/versionsshould be handled separately by a scheduled pipeline that opens automated pull requests.