feat(workflow): Add support to release for prod-preview|stable - #18
Open
mdsahiloss wants to merge 3 commits into
Open
feat(workflow): Add support to release for prod-preview|stable#18mdsahiloss wants to merge 3 commits into
mdsahiloss wants to merge 3 commits into
Conversation
mdsahiloss
marked this pull request as draft
July 23, 2026 15:02
mdsahiloss
marked this pull request as ready for review
July 23, 2026 15:04
mdsahiloss
force-pushed
the
mdsahiloss/qa-225
branch
2 times, most recently
from
July 27, 2026 07:03
4da1a4b to
d321bc6
Compare
* Also Add support for meta package Signed-off-by: Md Sahil <Sahil@unikraft.io>
Mirror the versioned package's depends/recommends/suggests into nfpm-meta.yaml, using unversioned ukp-* package names so the meta package pulls in the latest compatible siblings. Signed-off-by: Md Sahil <sahil@unikraft.io>
mdsahiloss
force-pushed
the
mdsahiloss/qa-225
branch
6 times, most recently
from
September 11, 2026 07:50
a162c48 to
12e6ed0
Compare
Build and publish the packages of the prod-staging branches as ukp0-*,
so prod-staging joins the same numbered-release scheme already used by
prod-stableN and prod-previewN. Only ukp0-* is published from
prod-staging: release 0 has no ukp-<component> meta package, so it
cannot pull a numbered release in as a dependency.
* Set RELEASE_VERSION=0 on prod-staging, so nfpm names the package
ukp0-<component> instead of the unversioned ukp-<component>.
* Skip the meta package for release 0, so prod-staging publishes the
ukp0-<component> package and nothing else.
* Add `replaces: ukp-<component> (<< ${SEMVER})` so the versioned
package takes over the files of the unversioned one that
prod-staging published until now.
* Make the meta package architecture-independent, matching the other
components, now that it is built on both amd64 and arm64.
* Let the staging build stand in for the newest numbered release, so a
release node can run individual components from staging. The ukp0-*
package gains a generated `provides` for ukpN-<component>, versioned
with `= ${SEMVER}` because an unversioned provides does not satisfy the
dependencies that carry a version constraint. Only the newest release is
named: a numbered release conflicts with ukp1-*..ukpN-1-*, and an
unversioned conflict also catches whatever provides that name, so naming
an older release would make ukp0-* collide with the very release it is
meant to sit alongside. No `conflicts` or `replaces` are declared against
ukpN-* either. Numbered releases never name ukp0-*, so none of this
reaches customers.
Signed-off-by: Md Sahil <Sahil@unikraft.io>
mdsahiloss
force-pushed
the
mdsahiloss/qa-225
branch
from
September 11, 2026 12:36
12e6ed0 to
5e81dd8
Compare
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
1 participant
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.
Add support to release for prod-(preview|stable)*
Depends on: https://github.com/unikraft-cloud/internal-actions/pull/30