Skip to content

bump: keycardai-oauth → 0.21.1 - #200

Merged
keycard-gh-workflows-access[bot] merged 1 commit into
mainfrom
bump/keycardai-oauth-0.21.1
Jul 20, 2026
Merged

bump: keycardai-oauth → 0.21.1#200
keycard-gh-workflows-access[bot] merged 1 commit into
mainfrom
bump/keycardai-oauth-0.21.1

Conversation

@keycard-gh-workflows-access

Copy link
Copy Markdown
Contributor

Auto-bump for keycardai-oauth to 0.21.1.

Generated by scripts/bump_package.py. The branch tag will be created at the squash-merge SHA after this PR merges, which triggers the publish workflow.

Auto-bump for keycardai-oauth.
@keycard-gh-workflows-access
keycard-gh-workflows-access Bot enabled auto-merge (squash) July 20, 2026 16:52

@Larry-Osakwe Larry-Osakwe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bump PR approved to unblock the 0.21.1 release; direct-merge refusal is being fixed in the bump script (ref fast-forward instead of merge API).

@keycard-gh-workflows-access
keycard-gh-workflows-access Bot merged commit 1eac350 into main Jul 20, 2026
5 checks passed
@keycard-gh-workflows-access
keycard-gh-workflows-access Bot deleted the bump/keycardai-oauth-0.21.1 branch July 20, 2026 17:31
Larry-Osakwe added a commit that referenced this pull request Jul 20, 2026
The ruleset bypass covers ref pushes but the PR merge API does not
exercise it: the app merges bump PRs on go-sdk by direct push while the
same app gets "base branch policy prohibits the merge" here (run
29761405739, PR #200). When the direct merge is refused, fast-forward
main to the PR head via the refs API; GitHub marks the PR merged and
the tag step proceeds at that SHA. Auto-merge stays armed and the
recovery pre-check still backstops both.

Co-authored-by: GitHub Action <action@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant