Skip to content

ci: give release verification 60 minutes and note v1.10.1 - #64

Merged
juicycleff merged 1 commit into
mainfrom
fix/release-verify-timeout
Oct 30, 2026
Merged

juicycleff merged 1 commit into
mainfrom
fix/release-verify-timeout

Conversation

@juicycleff

Copy link
Copy Markdown
Contributor

The v1.10.0 release run pushed the root tag, then timed out in the engine package's race tests (30 minutes) before it tagged any sub-module. So v1.10.0 exists for the root only, and api, extension, mcpbridge and the rest have no v1.10.0 tag.

This gives the release workflow's race tests 60 minutes, the same as CI coverage got in #63. On a hosted runner the engine and SQLite packages already take about 25 to 30 minutes each.

AGENTS.md says a rerun with the same tag stops at git tag, so once this merges, release the same code as v1.10.1:

gh workflow run release.yml --ref main -f tag=v1.10.1

The CHANGELOG gets a short 1.10.1 entry saying why, above the 1.10.0 section.

The v1.10.0 release run tagged the root module, then its race tests hit the 30-minute timeout in the engine package before any sub-module was tagged. Release verification now gets 60 minutes, the same as CI coverage. Because a rerun with v1.10.0 stops at the existing tag, the CHANGELOG adds a 1.10.1 entry for the same code.
@juicycleff
juicycleff merged commit be2e968 into main Oct 30, 2026
24 checks passed
@juicycleff
juicycleff deleted the fix/release-verify-timeout branch October 30, 2026 15:19
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