feat(ci): stop building stable-daily images#2208
Draft
renner0e wants to merge 2 commits into
Draft
Conversation
Up to standards ✅🟢 Issues
|
This comment was marked as outdated.
This comment was marked as outdated.
renner0e
added a commit
to get-aurora-dev/common
that referenced
this pull request
May 14, 2026
This was referenced May 14, 2026
This was referenced May 14, 2026
Member
Author
|
I want to get this merged in the next few days, I don't think the kcm and systemd service should be hard blockers as we will not get rid of the compatibility tag ever. |
These do not make super much sense, this is in preparation for the testing branches so we don't build too many images. We will still build stable images in PRs to find out if things are broken on those images only. To not break existing users, point this to `:stable` instead, effectively lying about the cadence now. We have to do it this way because stable-daily has ZFS and `:latest` doesn't to avoid breaking that use case. In the future when we have removed ZFS we can point this to `:latest`.
renner0e
force-pushed
the
retire-stable-daily
branch
from
c99e53d to
416ef5a
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
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.
These do not make super much sense, this is in preparation for the testing branches so we don't build too many images.
We will still build stable images in PRs to find out if things are broken on those images only.
To not break existing users, point this to
:stableinstead, effectively lying about the cadence now. We have to do it this way because stable-daily has ZFS and:latestdoesn't to avoid breaking that use case. In the future when we have removed ZFS we can point this to:latest.this makes this much easier to implement:
increment tag suffix for multiple daily builds #1833
remove tag from rebase-helper (feat: remove stable-daily in rollback-helper get-aurora-dev/common#177)
handle kcm_ublue (Remove stable-daily images from the kcm_ublue settings ledif/kcm_ublue#22)
reflect this change in the docs (chore: remove stable-daily from docs aurora-docs#373)
make a systemd service to rebase people from :stable-daily to :stable (kinda overkill and optional, compatibility tag we will have to keep forever anyway )
make a blog post about the change
anything else we should be doing?