Repository navigation
ci: allow release dependency tests time to compile on Windows - #53
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Windows release validator stops the Cargo dependency update integration test at Bun's default five-second timeout, preventing v0.1.6 publication. The test invokes real Cargo compilation and needs more time on hosted Windows runners.
Set the release workflow test timeout to 60 seconds. Assertions and package contents stay unchanged. After merging, dispatch the updated workflow on main against the existing v0.1.6 tag.
Validation:
bun test --timeout 60000 script/release.test.ts(3 passed);git diff --check.