chore(ci): migrate release pipeline fully to Forgejo #31
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
asmo/cashu-operator!31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/forgejo-release-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Moves the remaining GitHub dependencies out of the release process:
git.cashu.dev/asmo/cashu-operator:<tag>+:latest) using the automaticGITHUB_TOKEN(packages: write). Verified the registry is live on the instance (/v2/returnsdocker-distribution-api-version: registry/2.0).install.yamlwill embed the Forgejo image from the next release on.actions/deploy-pagesis unavailable on Forgejo); keptmkdocs build --strictas a CI check, now also on PRs.IMGexamples point at git.cashu.dev instead of asmogo.github.io / ghcr.io..opencode/skills/release/SKILL.mddocumenting the Forgejo release flow, updated for the new registry.Left unchanged on purpose: CRD group
mint.cashu.asmogo.github.io(API identity), the arkade processor ghcr image (separate upstream project), and the Go module path (renaming is a breaking change).