Skip to content

chore(deps): Bump bo4e-cli from 1.2.1 to 1.2.3#1067

Merged
lord-haffi merged 4 commits into
mainfrom
deps/bo4e-cli
Jun 5, 2026
Merged

chore(deps): Bump bo4e-cli from 1.2.1 to 1.2.3#1067
lord-haffi merged 4 commits into
mainfrom
deps/bo4e-cli

Conversation

@lord-haffi
Copy link
Copy Markdown
Collaborator

This fixes the issue with unexpected long GitHub tokens in GitHub Actions. See bo4e/BO4E-CLI#176

@lord-haffi lord-haffi self-assigned this Jun 5, 2026
lord-haffi and others added 3 commits June 5, 2026 08:29
The bo4e-cli regex still rejects the GitHub Actions installation
token even after lifting the length cap (bo4e-cli#176, v1.2.2).
Hypothesis: the new `ghs_…` tokens contain characters outside the
regex's [A-Za-z0-9_] body charset (`-`, `+`, `/`, `=`, …).

Add a sorted-character anagram of the body (everything after the
4-char prefix) to the [auth] line. The anagram reveals the character
multiset without leaking position, so we can confirm or refute the
hypothesis from the next CI failure log.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
v1.2.3 widens the token-validation regex body charset from
`[A-Za-z0-9_]` to `[A-Za-z0-9_.\-]`, accepting GitHub's new
JWT-encoded `ghs_…` Actions installation tokens (bo4e-cli#178).
Mirror the charset in the script's diagnostic regex so
`bo4e-regex-valid=True` lines up with the CLI's verdict again.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@lord-haffi lord-haffi changed the title chore(deps): Bump bo4e-cli from 1.2.1 to 1.2.2 chore(deps): Bump bo4e-cli from 1.2.1 to 1.2.3 Jun 5, 2026
@lord-haffi lord-haffi merged commit 15b7b8c into main Jun 5, 2026
27 checks passed
@lord-haffi lord-haffi deleted the deps/bo4e-cli branch June 5, 2026 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant