Repository navigation
fix(v0.7.73): preserve plugin command discovery in development environments - #72
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.
Plugin discovery previously ran a login shell, which could replace PATH and hide a host executable that the CLI could otherwise launch. Preserve the inherited PATH and quote executable names; add regression coverage for both behaviors.
Release 0.7.73 also moves the permission-sensitive production submission fixture onto a native temporary filesystem. Package versions, provider metadata, plugin projections and bun.lock are updated together.
Validation: build, typecheck, lint, full-only integration tests (39), Node dist checks and CLI artifact tests (2) passed. Default tests initially had 3 environment failures: two executable fixtures were placed on a noexec temporary mount and one Git fixture had a transient object-read failure. Re-running the affected plugin and article scenario suites passed all 12 cases; all other default batches passed. Executable fixtures use an executable TMPDIR for the follow-up run. Registry artifact preparation passed.