fix(ci): use safe inputs and versioned workflow releases #9
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows!9
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/forgejo-input-names"
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?
Forgejo resolves the reusable workflow's hyphenated input expression in runs-on to an empty label, leaving the Homelab/bundles consumer job waiting with no requested runner label.
This renames every reusable workflow_call input to an underscore identifier and updates all expressions, examples, and documentation. A contract test now rejects hyphenated input identifiers and expressions so runner, library, registry, and deployment inputs cannot regress.
Validation:
Follow-up after merge:
Relates to #3.
Release policy update: consumer repositories will use readable immutable semantic version tags such as v1.0.0 in both uses and library_ref. They will not contain raw workflow commit hashes or track main. Build receipts resolve the selected tag to its commit SHA internally for provenance.
The release protocol is documented in docs/releases.md: merge through protected main, publish the next unused vMAJOR.MINOR.PATCH tag, never move or reuse a published tag, and update consumers through reviewed pull requests.
Follow-up after this PR merges: publish v1.0.0, update Homelab/bundles PR #3 to v1.0.0 and the underscore input names, then rerun its consumer check.
fix(ci): use Forgejo-safe workflow input namesto fix(ci): use safe inputs and versioned workflow releases