Skip to content

Fix Docker image tagging confusion with conditional logic#1184

Open
kevinschaper wants to merge 1 commit intomainfrom
fix-docker-image-tagging
Open

Fix Docker image tagging confusion with conditional logic#1184
kevinschaper wants to merge 1 commit intomainfrom
fix-docker-image-tagging

Conversation

@kevinschaper
Copy link
Member

Summary

Fixes the issue where main branch pushes were incorrectly tagged with old release versions, causing confusion about when releases were actually happening.

Changes

Simple conditional fix using github.event_name:

  • For releases (github.event_name == "release"): Tag with latest and actual release version
  • For main branch pushes: Tag with latest-dev and branch-specific tags (no latest tag)

Benefits

  • No more confusing release tags: Main branch pushes won't create images tagged with old release versions
  • Clear separation: latest tag only used for actual releases, latest-dev for development
  • Minimal change: Single workflow modification instead of restructuring everything
  • Same functionality: Dev deployment and release processes work exactly the same

Before/After

Before: Main branch push → Image tagged with latest, v1.2.3 (old release), and SHA
After: Main branch push → Image tagged with latest-dev, main-<sha>, and SHA

Before: Release published → Image tagged with latest, v1.2.3 (old release), and SHA
After: Release published → Image tagged with latest, v1.4.0 (actual release), and SHA

This approach solves the core problem with the absolute minimum change required.

🤖 Generated with Claude Code

…n event type

- Use github.event_name to distinguish between releases and main branch pushes
- For releases: tag with 'latest' and actual release version
- For main branch: tag with 'latest-dev' and branch-specific tags (no 'latest')
- Eliminates the issue where main branch pushes were incorrectly tagged with old release versions

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@netlify
Copy link

netlify bot commented Aug 1, 2025

Deploy Preview for monarch-app ready!

Name Link
🔨 Latest commit c84970a
🔍 Latest deploy log https://app.netlify.com/projects/monarch-app/deploys/688d0d8673577a00088b6b32
😎 Deploy Preview https://deploy-preview-1184--monarch-app.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@codecov
Copy link

codecov bot commented Aug 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.07%. Comparing base (ed8a58f) to head (c84970a).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1184   +/-   ##
=======================================
  Coverage   72.07%   72.07%           
=======================================
  Files          92       92           
  Lines        3255     3255           
=======================================
  Hits         2346     2346           
  Misses        909      909           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments