[PR #1405] [MERGED] fix: update publish workfow to only tag stable versions latest #1610

Closed
opened 2026-02-26 19:33:59 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/documenso/documenso/pull/1405
Author: @david-loe
Created: 10/16/2024
Status: Merged
Merged: 11/12/2024
Merged by: @Mythie

Base: mainHead: main


📝 Commits (3)

  • 99edc01 Update publish workfow to only tag stable versions latest
  • c8a86ce chore: also tag rc releases on docker
  • 5674497 fix: actually remember what the rc format looks like

📊 Changes

1 file changed (+41 additions, -15 deletions)

View changed files

📝 .github/workflows/publish.yml (+41 -15)

📄 Description

Description

This pull request introduces modifications to the GitHub Actions workflow to ensure that the latest Docker tag is only pushed for stable releases. It prevents the latest tag from being assigned to release candidates (-rc), beta versions, or other pre-release tags. This enhancement improves version management by keeping the latest tag reserved exclusively for fully stable versions (e.g., 1.0.0).

Fixes #1404

Changes Made

  • Added a conditional check to verify if the release version follows the format X.Y.Z (stable release format).
  • Updated the Docker manifest creation steps to only push the latest tag if the version is a stable full release.
  • Modified both DockerHub and GitHub Container Registry push steps to reflect the new versioning conditions.

Checklist

  • I have tested these changes locally and they work as expected.
  • I have added/updated tests that prove the effectiveness of these changes.
  • I have updated the documentation to reflect these changes, if applicable.
  • I have followed the project's coding style guidelines.

Summary by CodeRabbit

  • Chores
    • Enhanced GitHub Actions workflow for publishing Docker images with a stability check for the latest tag.
    • Streamlined the process by removing redundant lines, ensuring the latest tag is only pushed for stable application versions.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/documenso/documenso/pull/1405 **Author:** [@david-loe](https://github.com/david-loe) **Created:** 10/16/2024 **Status:** ✅ Merged **Merged:** 11/12/2024 **Merged by:** [@Mythie](https://github.com/Mythie) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (3) - [`99edc01`](https://github.com/documenso/documenso/commit/99edc01b03f1a1fd1c213c0e99329dd394070a6e) Update publish workfow to only tag stable versions latest - [`c8a86ce`](https://github.com/documenso/documenso/commit/c8a86ce5e27dc5dfa204e5bdeb19b624c6ac67b5) chore: also tag rc releases on docker - [`5674497`](https://github.com/documenso/documenso/commit/567449745a5a276e72e51e02115d68aca6081e07) fix: actually remember what the rc format looks like ### 📊 Changes **1 file changed** (+41 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/publish.yml` (+41 -15) </details> ### 📄 Description ## Description This pull request introduces modifications to the GitHub Actions workflow to ensure that the `latest` Docker tag is only pushed for stable releases. It prevents the `latest` tag from being assigned to release candidates (`-rc`), beta versions, or other pre-release tags. This enhancement improves version management by keeping the `latest` tag reserved exclusively for fully stable versions (e.g., `1.0.0`). ## Related Issue Fixes #1404 ## Changes Made - Added a conditional check to verify if the release version follows the format `X.Y.Z` (stable release format). - Updated the Docker manifest creation steps to only push the `latest` tag if the version is a stable full release. - Modified both DockerHub and GitHub Container Registry push steps to reflect the new versioning conditions. ## Checklist - [x] I have tested these changes locally and they work as expected. - [x] I have added/updated tests that prove the effectiveness of these changes. - [x] I have updated the documentation to reflect these changes, if applicable. - [x] I have followed the project's coding style guidelines. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Enhanced GitHub Actions workflow for publishing Docker images with a stability check for the `latest` tag. - Streamlined the process by removing redundant lines, ensuring the `latest` tag is only pushed for stable application versions. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 19:33:59 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#1610
No description provided.