Skip to content

fix(release): check repository API access - #1465

Merged
Chemaclass merged 1 commit into
mainfrom
fix/release-check-github-api
Nov 8, 2026
Merged

Chemaclass merged 1 commit into
mainfrom
fix/release-check-github-api

Conversation

@Chemaclass

Copy link
Copy Markdown
Member

Background

Release preflight aborts when the GitHub homepage takes more than five seconds to answer, even when Git and the authenticated repository API work. Check the repository API used by publishing so an unrelated homepage timeout does not block a release.

Changes

  • Use the authenticated GitHub CLI to check repository API access.
  • Keep preflight failures fatal and name the repository API in the error.
  • Cover an unavailable homepage with a working API, and an API failure with a working homepage.

Validation: the regression failed on the old check; the release validation file passes in plain and strict modes (29 tests, 31 assertions). ShellCheck, lint, and a live API check passed.

Checklist

  • I updated the CHANGELOG.md to reflect the fix
  • Documentation reviewed: no user-facing usage change

@Chemaclass Chemaclass added the bug Something isn't working label Nov 8, 2026
@Chemaclass Chemaclass self-assigned this Nov 8, 2026
@Chemaclass
Chemaclass enabled auto-merge November 8, 2026 11:51
@Chemaclass
Chemaclass disabled auto-merge November 8, 2026 11:54
@Chemaclass
Chemaclass merged commit 217201c into main Nov 8, 2026
38 checks passed
@Chemaclass
Chemaclass deleted the fix/release-check-github-api branch November 8, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant