Skip to content

fix: v1.7.1 patch — tier persistence, Ctrl-C guards, version string#10

Merged
cody-rester merged 1 commit into
itential:mainfrom
cody-rester:fix/v1-7-1
May 11, 2026
Merged

fix: v1.7.1 patch — tier persistence, Ctrl-C guards, version string#10
cody-rester merged 1 commit into
itential:mainfrom
cody-rester:fix/v1-7-1

Conversation

@cody-rester

Copy link
Copy Markdown
Contributor

Description

Patch release bundling three bug fixes found during a polish pass before shipping 1.7.1.

Type of Change

  • Bug fix

Changes Made

  • tier set persistence fix — when the active environment has its own tier field, the environment overlay (priority 3 in tier resolution) was silently overwriting any change made to config.json (priority 4) on every subsequent load. _persist_tier now propagates the new tier to the environment file when the env carries an explicit tier override. Also tightened the "already set" check to use ctx().tier (the effective resolved tier) rather than the raw config.json value.
  • env edit Ctrl-C guards — the Gateway4 URI, username, and password prompts in handle_env_edit used bare if value: checks after .ask(). Pressing Ctrl-C returned None from questionary, which silently skipped the field and continued to the next prompt, trapping the user mid-flow. Each prompt now checks if value is None: raise KeyboardInterrupt.
  • config init Ctrl-C guard — the "Create another environment?" loop used if not add_more: which treated a None return (Ctrl-C) as True, breaking the loop silently instead of raising. Added the explicit None check before the break.
  • Version string_version.py was still "1.7" from the 1.7.0 release; bumped to "1.7.1" so --version output matches the package.

Testing

  • Manually reproduced the tier set persistence bug (env with tier: extended overlay, tier set standard appeared to succeed but tier show still showed extended). Verified fix resolves it.
  • Ctrl-C behavior verified against the project pattern documented in CLAUDE.md.

Checklist

  • Code follows the project's style guidelines
  • Self-review of code has been performed
  • Code has been commented where necessary
  • Tested with make setup or relevant profile
  • Commits follow conventional format (type: subject)
  • No secrets or credentials committed
  • Documentation has been updated accordingly
  • PR has been labeled appropriately (enhancement, bug, documentation, refactor, chore)

- 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
@cody-rester cody-rester added the bug Something isn't working label May 11, 2026
@cody-rester cody-rester requested a review from a team as a code owner May 11, 2026 11:27
@cody-rester cody-rester merged commit 65beaf9 into itential:main May 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant