Repository navigation
Conversation
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
# Conflicts: # .github/workflows/auto-release.yml
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe pull request modifies GitHub Actions CI/CD workflows to capture and share the draft release tag between jobs. The auto-release workflow now writes the draft tag to an artifact, which the release workflow downloads and exposes as an output. Additionally, Docker publishing is enhanced with an updated latest tag option and additional authenticated credentials. Changes
Sequence DiagramsequenceDiagram
participant AutoRelease as auto-release<br/>Workflow
participant Artifact as GitHub<br/>Artifacts
participant Release as release<br/>Workflow
participant Docker as Docker<br/>Registry
AutoRelease->>AutoRelease: Generate draft tag
AutoRelease->>Artifact: Write draft_tag.txt & upload artifact
Release->>Artifact: Download draft_tag artifact
Release->>Release: Read & expose draft_tag output
Release->>Docker: Publish with add_latest: true<br/>(using DOCKER_USERNAME_2)
Docker-->>Release: Image published
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|




Summary by CodeRabbit