Put minimum release age first and use a one-day Cautious preset - #732
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 release-age submenu currently asks for dependency scope before the cooldown and offers a 3-day Cautious preset. Show and focus Minimum release age first, followed by Release-age scope, with keyboard navigation matching that order.
Change Cautious to 1 day (86,400 seconds) in both configuration wizards. Existing 3-day overrides remain custom values.
Validation: terminal regressions failed before the fix and pass afterward; Rust 1.94.0 workspace build, formatting, Clippy, and fast PR test gate; all 14,309 tests in the full isolated suite; the audit fixture; dependency policy, installer, and npm release checks. No performance-sensitive paths changed.
An unrelated IPv6 listener test timed out once, then passed in isolation and in the complete 6,300-test rerun.
macOS CI passed on retry after an unrelated
outdatedscheduling test recorded 457 ms against a 450 ms limit. That test also passed in the full local suite and a targeted rerun. All current-commit CI checks are green.Finding ledger: 0 received, 0 verified, 0 rejected, 0 blocked, 0 pending.
Generated by OpenAI Codex (
GPT-6) using the Codex agent harness.