Skip to content

Fix CI to publish Canasta version tag#600

Merged
yaronkoren merged 1 commit intomasterfrom
fix-ci-version-tag
Mar 2, 2026
Merged

Fix CI to publish Canasta version tag#600
yaronkoren merged 1 commit intomasterfrom
fix-ci-version-tag

Conversation

@cicalese
Copy link
Contributor

@cicalese cicalese commented Mar 2, 2026

Summary

  • Add fetch-depth: 2 to the checkout step in the Docker build workflow so that git diff HEAD~1 can detect VERSION file changes
  • Without this, the shallow clone has no parent commit, so the version tag (e.g., 3.3.1) is never published to ghcr.io/canastawiki/canasta

Fixes #599

The checkout step defaults to fetch-depth: 1 (shallow clone), so
HEAD~1 does not exist and the git diff that detects VERSION file
changes silently fails. Add fetch-depth: 2 so the previous commit
is available for comparison.

Fixes #599
@github-actions
Copy link

github-actions bot commented Mar 2, 2026

🐳 The image based on f9c26b35 commit has been built with 1.43.6-20260302-600 tag as ghcr.io/canastawiki/canasta:1.43.6-20260302-600

@yaronkoren yaronkoren merged commit c0f7c1c into master Mar 2, 2026
2 checks passed
@yaronkoren yaronkoren deleted the fix-ci-version-tag branch March 2, 2026 14:22
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.

CI workflow never publishes Canasta version tag

2 participants