Skip to content

ci: adapt release workflow for t11z fork#1

Merged
t11z merged 1 commit into
mainfrom
ci/adapt-release-workflow-for-fork
Apr 4, 2026
Merged

ci: adapt release workflow for t11z fork#1
t11z merged 1 commit into
mainfrom
ci/adapt-release-workflow-for-fork

Conversation

@t11z
Copy link
Copy Markdown
Owner

@t11z t11z commented Apr 4, 2026

Summary

  • Removes the deploy job (MongoDB db:update script — no hosted API in the fork)
  • Removes the trigger-downstream job (no downstream repo to notify)
  • Consolidates into a single container-release job with the repo guard updated to t11z/5e-database
  • Tag resolution (release event vs workflow_dispatch) moved inline to container-release

Test plan

  • Merge and publish a GitHub Release — confirm container-release runs and pushes ghcr.io/t11z/5e-database:{tag} + :latest
  • Trigger via workflow_dispatch — confirm it picks up the latest release tag via gh api

🤖 Generated with Claude Code

Remove deploy (MongoDB update) and trigger-downstream jobs — the fork
has no hosted API. Consolidate into a single container-release job that
builds and pushes ghcr.io/t11z/5e-database:{tag} + :latest on release
publish or manual dispatch.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Owner Author

@t11z t11z left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Deploy and the downstream trigger are gone, the guard points to t11z/5e-database, tag resolution is inline, and the GitHub Actions run with both tags

@t11z t11z self-assigned this Apr 4, 2026
@t11z t11z merged commit aba77ae into main Apr 4, 2026
6 checks passed
@t11z t11z deleted the ci/adapt-release-workflow-for-fork branch April 4, 2026 23:15
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