Skip to content

Fix PowerShell PATH refresh and integration upgrades - #14

Open
CheckPickerUpper wants to merge 1 commit into
masterfrom
codex/issue-5-powershell-upgrade
Open

CheckPickerUpper wants to merge 1 commit into
masterfrom
codex/issue-5-powershell-upgrade

Conversation

@CheckPickerUpper

Copy link
Copy Markdown
Owner

Summary

  • refresh the current PowerShell process PATH even when the install directory is already in persisted user PATH
  • normalize PATH comparisons to avoid duplicate entries across Windows path spellings
  • replace existing managed profile blocks so legacy bare-rep integrations migrate to the guarded resolver
  • retain an actionable recovery function when the binary is genuinely unavailable

Closes #5

Verification

  • cargo test --all-targets
  • static installer assertions

Note: a Windows PowerShell fresh-session run is still required for full platform-specific verification; this Linux workspace has no PowerShell runtime.

@github-actions

Copy link
Copy Markdown

Visual recap — skipped

The visual recap job did not run for this pull request. This is informational only and does not block the PR.

Recap skipped for 3998d43: VISUAL_RECAP_API_KEY not configured (openai-compatible backend).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows PowerShell upgrades can leave RePortal commands broken when PATH is stale

1 participant