-
Notifications
You must be signed in to change notification settings - Fork 123
chore: migrate Homebrew cask tap from openshift-pipelines to tektoncd #2565
Copy link
Copy link
Open
Labels
tektoncd-migrationTasks related to tektoncd org migrationTasks related to tektoncd org migration
Description
Context
The PAC Homebrew cask is currently published to openshift-pipelines/homebrew-pipelines-as-code via GoReleaser. This tap repo and the GoReleaser config need to be migrated to tektoncd.
Current config in .goreleaser.yml:79–106
homebrew_casks:
- name: tektoncd-pac
repository:
owner: openshift-pipelines # ← change to tektoncd
name: homebrew-pipelines-as-code # ← update to tektoncd tap repo nameSteps
- Create or transfer
openshift-pipelines/homebrew-pipelines-as-code→tektoncd/homebrew-pipelines-as-code(or equivalent tap name agreed on by the tektoncd community) - Update
.goreleaser.ymlrepository.ownertotektoncdandrepository.nameto the new tap repo name - Ensure the GoReleaser bot token (stored in repo secrets) has write access to the new tap repo under
tektoncd - Verify cask install works after next release:
brew install tektoncd/pipelines-as-code/tektoncd-pac
Notes
- Users currently using
brew install openshift-pipelines/pipelines-as-code/tektoncd-pacwill need to update their tap. - Consider adding a deprecation notice or redirect in the old tap if it remains accessible.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
tektoncd-migrationTasks related to tektoncd org migrationTasks related to tektoncd org migration