Skip to content

fix: improving stage skipping for releasing - #95

Merged
RobPasMue merged 2 commits into
mainfrom
fix/stage-skipping
Sep 11, 2026
Merged

RobPasMue merged 2 commits into
mainfrom
fix/stage-skipping

Conversation

@RobPasMue

Copy link
Copy Markdown
Member

Issues were due mostly to the dependency definition between stages. The following changes were made:

  • release stage required all previous stages to succeed. Since pre-commit was being skipped, this triggered the release stage to be skipped as well... thus requiring the always() condition as well
  • making Docker push permissions explicit in the docker stage
  • docker stage conditions were adapted so that scheduled runs continue to go through but if a release is being performed, it requires the release stage to succeed as well

@RobPasMue RobPasMue self-assigned this Sep 11, 2026
@RobPasMue
RobPasMue requested a review from margalva as a code owner September 11, 2026 06:02
@github-actions github-actions Bot added maintenance Operation not directly changing the production code - e.g., updating a devops pipeline fixed bug Something isn't working labels Sep 11, 2026
@RobPasMue
RobPasMue merged commit 002fa13 into main Sep 11, 2026
14 of 15 checks passed
@RobPasMue
RobPasMue deleted the fix/stage-skipping branch September 11, 2026 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working fixed maintenance Operation not directly changing the production code - e.g., updating a devops pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants