fix: v1.7.1 patch — tier persistence, Ctrl-C guards, version string#10
Merged
Conversation
- tier set now propagates to the active environment file when the env carries its own tier override, preventing the env overlay from silently reverting config.json on every subsequent load - env edit Gateway4 prompts now raise KeyboardInterrupt on Ctrl-C instead of silently skipping fields and continuing - config init "create another environment" loop now raises KeyboardInterrupt on Ctrl-C instead of breaking silently - _version.py bumped to 1.7.1 (was still "1.7" from the 1.7.0 release) - pyproject.toml version bumped to 1.7.1 - CHANGELOG.md updated with 1.7.1 entry
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
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.
Description
Patch release bundling three bug fixes found during a polish pass before shipping 1.7.1.
Type of Change
Changes Made
tier setpersistence fix — when the active environment has its owntierfield, the environment overlay (priority 3 in tier resolution) was silently overwriting any change made toconfig.json(priority 4) on every subsequent load._persist_tiernow propagates the new tier to the environment file when the env carries an explicittieroverride. Also tightened the "already set" check to usectx().tier(the effective resolved tier) rather than the rawconfig.jsonvalue.env editCtrl-C guards — the Gateway4 URI, username, and password prompts inhandle_env_editused bareif value:checks after.ask(). Pressing Ctrl-C returnedNonefrom questionary, which silently skipped the field and continued to the next prompt, trapping the user mid-flow. Each prompt now checksif value is None: raise KeyboardInterrupt.config initCtrl-C guard — the "Create another environment?" loop usedif not add_more:which treated aNonereturn (Ctrl-C) asTrue, breaking the loop silently instead of raising. Added the explicitNonecheck before the break._version.pywas still"1.7"from the 1.7.0 release; bumped to"1.7.1"so--versionoutput matches the package.Testing
tier setpersistence bug (env withtier: extendedoverlay,tier set standardappeared to succeed buttier showstill showed extended). Verified fix resolves it.Checklist
make setupor relevant profiletype: subject)enhancement,bug,documentation,refactor,chore)