fix(brew): use brew updater after release is public

[arpad-csepi]

No description provided.

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf CI / verify-proto (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	⏩ skipped	✅ passed	Nov 19, 2025, 2:12 PM

[ramizpolic]

@arpad-csepi do you know why the CI pipelien doesnt run when github-bot opens a PR? This is a separate issue, but the pipeline never runs and we have to recreate the PR under personal name for CI to run

[arpad-csepi]

@arpad-csepi do you know why the CI pipelien doesnt run when github-bot opens a PR? This is a separate issue, but the pipeline never runs and we have to recreate the PR under personal name for CI to run

We are opening the PR with the CI using the GITHUB_TOKEN and this behavior is expected to avoid cilcular CI calls.
I modified the brew workflow to only open a PR if the brew test passes. Do we need to run the CI to be able to merge the brew changes? The other tests in the CI are not useful for these hash changes.

Source: https://github.com/marketplace/actions/add-commit#the-commit-from-the-action-is-not-triggering-ci

[arpad-csepi]

@arpad-csepi do you know why the CI pipelien doesnt run when github-bot opens a PR? This is a separate issue, but the pipeline never runs and we have to recreate the PR under personal name for CI to run

We are opening the PR with the CI using the GITHUB_TOKEN and this behavior is expected to avoid cilcular CI calls. I modified the brew workflow to only open a PR if the brew test passes. Do we need to run the CI to be able to merge the brew changes? The other tests in the CI are not useful for these hash changes.

Source: https://github.com/marketplace/actions/add-commit#the-commit-from-the-action-is-not-triggering-ci

Managed to find a workaround to use PAT token as GTIHUB_TOKEN for the CI by closing the reopening the brew update PR by hand. In this way the CI is triggered and the we are able to merge the changes as the Status check will be success.
Added a disclaimer to the automated PR description as a guidence. WDYT @ramizpolic , is it acceptable solution? The other solution can be to create an org account and use that account PAT token for commits.

[ramizpolic]

@arpad-csepi We have a couple of org-wide accounts that we can use here to bump the version. WDYT if we use a new GH_PR_TOKEN for creating PRs? This way, when we fork the repo, we can also create this secret to make it work.

Can you confirm that, if we use a custom account with GH_PR_TOKEN, once the brew update PR is created, the pipeline will run?

[arpad-csepi]

@arpad-csepi We have a couple of org-wide accounts that we can use here to bump the version. WDYT if we use a new GH_PR_TOKEN for creating PRs? This way, when we fork the repo, we can also create this secret to make it work.

Can you confirm that, if we use a custom account with GH_PR_TOKEN, once the brew update PR is created, the pipeline will run?

Confirmed that a custom account can be used with its own token to open a PR and trigger the CI workflow automatically.