Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

test(packaging): correct the rationale for -ExecutionPolicy Bypass

AkitaOnRails4572cac1d6f3
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 39a32262..34f915d0 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
+### Fixed
+- The Windows packaging test for the PowerShell wrapper now runs it with
+ `-ExecutionPolicy Bypass`. `-File` loads a script from disk and execution
+ policy governs script files, so on a machine at the Windows client default
+ of `Restricted` the unsigned wrapper was refused and the test failed for a
+ reason unrelated to what it asserts. Test-only; no shipped behaviour
+ changes. (#449)
+
### Added
- Windows tests moved to their own workflow
(`.github/workflows/windows.yml`), running on every push to `main`,
diff --git a/crates/ai-memory-cli/tests/packaging.rs b/crates/ai-memory-cli/tests/packaging.rs
index 77dd3ca7..dd599af2 100644
--- a/crates/ai-memory-cli/tests/packaging.rs
+++ b/crates/ai-memory-cli/tests/packaging.rs
@@ -1462,11 +1462,14 @@ fn powershell_wrapper_forwards_subscription_oauth_tokens_without_putting_values_
];
let mut command = Command::new("powershell.exe");
command
- // -ExecutionPolicy Bypass: bin/ai-memory.ps1 is an unsigned local script, so a machine
- // left on the Windows client default of `Restricted` refuses to load it and the wrapper
- // never runs (`UnauthorizedAccess`), failing this test for a reason unrelated to what it
- // checks. Every other PowerShell invocation in the repo already passes Bypass; this one
- // did not.
+ // -ExecutionPolicy Bypass: `-File` loads a script from disk, and execution policy
+ // governs script *files*, so on a machine left at the Windows client default of
+ // `Restricted` the unsigned bin/ai-memory.ps1 is refused (`UnauthorizedAccess`) and
+ // the wrapper never runs — failing this test for a reason unrelated to what it
+ // checks. The other in-repo invocation (render_shared.rs) uses `-Command`, which is
+ // not policy-gated and therefore needs no override; the generated hook commands pass
+ // Bypass defensively. GitHub's runner is permissive enough that this passes there
+ // today, so the fix is for running the suite on a stock Windows install.
.args([
"-NoLogo",
"-NoProfile",