Skip to content

fix: build and publish the chart when a parent build was skipped - #27

Merged
eksrha merged 1 commit into
mainfrom
fix/chart-build-condition
Nov 3, 2026
Merged

eksrha merged 1 commit into
mainfrom
fix/chart-build-condition

Conversation

@eksrha

@eksrha eksrha commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Problem

In the Release run after #25, chart-release succeeded and created the draft chart/202611.3.1, but chart-build was skipped, so the chart was never packaged, pushed or published.

chart-build has no status function in its if, which means an implicit success(). That checks the whole chain of ancestors: chart-release depends on tei-build, which is skipped when the TEI Containerfiles did not change, so chart-build was skipped as well.

Fix

chart-build now uses !cancelled() && needs.chart-release.result == 'success' && needs.chart-release.outputs.release-id != ''.

After merge

Merging does not release the chart by itself (no chart path changes). Delete the stale draft chart/202611.3.1 (it has no tag), then run the Release workflow manually with components=chart.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Possible relctl commands for this Pull Request

Version scheme: calver. The version of the release is the date of the release (YYYYMM.D.N, N counts the releases of that day). Branch prefixes and comment commands have no effect.

Need more help?

Have a look at my repo

This message was created by relctl and can be disabled by the env variable RELCTL_SILENT=true

@eksrha
eksrha merged commit 3bd0c85 into main Nov 3, 2026
3 checks passed
@eksrha
eksrha deleted the fix/chart-build-condition branch November 3, 2026 09:20
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