Repository navigation
feat(v2): verify independent package updates - #55
Merged
Merged
Conversation
Keep V1 defaults while adding a pinned V2 binary and updater lane. Require both package builds before publication and reject recipe-level shell injection. Consumer activation remains gated by runtime checks.
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.
Outcome
Pin official OpenCode V2 2.0.27 and make V2 updates independently verifiable. Preserve the V1 package, updater and default selection.
package-buildjob.Verification
bash tests/opencode-v2-contract.sh— pass; observed failing assertions before implementation and quoting fix.packages.opencode-v2build — pass,opencode v2.0.27.Dependencies and rollback
This leaf PR does not activate a host. It must merge and publish before the consumer can pin the updated artifact. Merge permission is separate from publication of this PR.
The Desktop backend candidate still has failing Ponytail/plugin/permission integration checks. Consumer deployment is blocked; no claim that the whole migration is green. Optional Context Fold/sidebar trials remain disabled and unverified. V1 databases and the controlling session are unchanged.
Rollback this leaf version/consumer pin through source; keep the V1 lane and matching recovery generation. No automatic history import.