fix: configure release smoke budget - #49
Merged
Merged
Conversation
PerishCode
marked this pull request as ready for review
July 10, 2026 05:15
PerishCode
pushed a commit
that referenced
this pull request
Aug 1, 2026
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.
What changed
input_budget_bytesWhy
v0.1.0-beta.23built and published successfully, but all three release smoke jobs timed out waiting for health because the shared temporary provider profile predated the new fail-closed budget requirement.Validation
v0.1.0-beta.23: install, help, service health, shutdown, and uninstall passeddeno fmt --config .runseal/deno.json --check .runsealdeno lint --config .runseal/deno.json .runsealdeno check --config .runseal/deno.json .runseal/wrappers/release.tsflavor check