Skip to content

Corrected behavior of defaulting to full, also for tags#147

Merged
simonmicro merged 2 commits intonextfrom
bug/tagged-full-by-default
May 1, 2026
Merged

Corrected behavior of defaulting to full, also for tags#147
simonmicro merged 2 commits intonextfrom
bug/tagged-full-by-default

Conversation

@simonmicro
Copy link
Copy Markdown
Member

...this is true for the main/next ones, but I somehow messed that up for the tagged ones (which default no-suffix to the minimal variant)

@simonmicro simonmicro requested a review from Copilot May 1, 2026 09:18
@simonmicro simonmicro self-assigned this May 1, 2026
@simonmicro simonmicro added the bug Something isn't working label May 1, 2026
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adjusts Docker image tagging for release/tag builds so the default (no suffix) tag points to the full image variant, aligning version-tag behavior with existing main/next workflows.

Changes:

  • Publish ${{ github.ref_name }} (no suffix) tags from the full build step in bake_to_version.yml.
  • Stop publishing ${{ github.ref_name }} (no suffix) tags from the minimal build step, leaving only -minimal tags there.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@simonmicro simonmicro changed the base branch from main to next May 1, 2026 09:34
@simonmicro simonmicro merged commit 3573537 into next May 1, 2026
6 checks passed
@simonmicro simonmicro deleted the bug/tagged-full-by-default branch May 1, 2026 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants