Skip to content

chore: migrate Homebrew cask tap from openshift-pipelines to tektoncd #2565

@chmouel

Description

@chmouel

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 name

Steps

  1. Create or transfer openshift-pipelines/homebrew-pipelines-as-codetektoncd/homebrew-pipelines-as-code (or equivalent tap name agreed on by the tektoncd community)
  2. Update .goreleaser.yml repository.owner to tektoncd and repository.name to the new tap repo name
  3. Ensure the GoReleaser bot token (stored in repo secrets) has write access to the new tap repo under tektoncd
  4. 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-pac will need to update their tap.
  • Consider adding a deprecation notice or redirect in the old tap if it remains accessible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    tektoncd-migrationTasks related to tektoncd org migration

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions