chore(mima): adapt pipeline for mimacom release process (DCS-21) - #1
Merged
Conversation
jcbadillo
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Onboarding of
function-kroto the mimacom registry (DCS-21).Adapts the upstream CI so the fork publishes signed packages to
ghcr.io/mimacom.ci.yml: trigger onmima/mima-release-*/v*tags (replacesmain)ci.yml: pin Crossplane CLI channel tostablefor reproducible buildsci.yml:contents: writeon the publish job, needed to create the GitHub Releaseci.yml: derive the package version from the tag onv*buildsci.yml: gate GHCR push + cosign signing on release branches and tagsci.yml: add CodeQL job, aligning with the rest of the fleetSECURITY.mdandrelease/cosign.pubChecklist
mimauses:pins left untouched (no gratuitous divergence from upstream)XPKG_ACCESS_ID(Upbound credential we do not use)--tlog-upload=false(air-gapped verification)