Add GitHub releases with patch version bumps for scheduled security builds#653
Merged
Conversation
- main.yml: Trigger on tag pushes (noble-*, jammy-*) instead of manual release published events - main.yml: Add step to create GitHub release after image build+push - main.yml: Add contents:write + packages:write permissions - main.yml: Update docker/build-push-action from v5 to v6 - scheduled-build.yml: Update docker/build-push-action from v5 to v6 - stale.yml: Remove deprecated repo-token parameter Co-authored-by: samip5 <1703002+samip5@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add GitHub releases creation for images
Auto-create GitHub releases on tag push and update deprecated workflow components
Feb 27, 2026
…ed workflow components - scheduled-build.yml: Create GitHub release after each weekly security rebuild with date-stamped tag (e.g. noble-1.0.2-security.20260227) - scheduled-build.yml: Add date-stamped Docker image tags alongside existing version and codename tags - scheduled-build.yml: Bump permissions to contents:write for release creation - scheduled-build.yml: Exclude security-tagged releases from base version lookup to prevent nested tags - main.yml: Update docker/build-push-action from v5 to v6 - scheduled-build.yml: Update docker/build-push-action from v5 to v6 - stale.yml: Remove deprecated repo-token parameter Co-authored-by: samip5 <1703002+samip5@users.noreply.github.com>
Copilot
AI
changed the title
Auto-create GitHub releases on tag push and update deprecated workflow components
Create GitHub releases for scheduled weekly security builds
Feb 27, 2026
The scheduled weekly security build now bumps the patch version (e.g. noble-1.0.2 -> noble-1.0.3) instead of appending -security.YYYYMMDD. Each rebuild creates a proper GitHub release with the new patch tag and pushes Docker images accordingly. Co-authored-by: samip5 <1703002+samip5@users.noreply.github.com>
Copilot
AI
changed the title
Create GitHub releases for scheduled weekly security builds
Add GitHub releases with patch version bumps for scheduled security builds
Feb 27, 2026
samip5
approved these changes
Feb 27, 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
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.
The weekly scheduled security rebuild pushes updated Docker images but creates no GitHub releases, making these rebuilds invisible to users tracking releases.
Scheduled build (
scheduled-build.yml)noble-1.0.2→noble-1.0.3) instead of inventing a separate tag scheme<codename>-<major>.<minor>.<patch>contents: writepermission: Required forgh release createExample flow:
Housekeeping
docker/build-push-actionv5 → v6 in bothmain.ymlandscheduled-build.ymlrepo-tokenfromstale.yml(actions/stale@v9 usesGITHUB_TOKENby default)✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.