polyengine 0.6.3; @polymorph/* 0.6.0; @polymorph/iroh 0.6.0 - #103
Merged
Conversation
Move host-polyengine's caret constraints to the polyengine v0.6.3
lockstep line, @polyengine/protocol ^0.3.1, and the sibling host
modules @polymorph/{webcrypto,websocket,webrtc-datachannels} ^0.6.0
(their protocol line moved with polyengine's); the relay-ws experiment
config takes the same versions as exact pins. Both locks resolve one
runtime family version and one protocol version.
polyengine 0.6.0 removed CliOptions.passthrough with no replacement
sink, so the exam's EXAM_GUEST_LOGS knob (live guest stdout/stderr on
the console) goes with it; the captured text stays reachable through
the instance's stdout()/stderr().
@polymorph/iroh 0.5.1 -> 0.6.0: the protocol minor bump is breaking
under the caret-honest scheme.
Gates: polyengine-setup (--frozen), deno task check (both configs),
exam-polyengine (pin drift, identity gate, 10/10 scenarios),
deno publish --dry-run, just check.
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
2 participants
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.
Move
host-polyengine's caret constraints to polyengine 0.6.3,@polyengine/protocol@^0.3.1, and the sibling host modules@polymorph/{webcrypto,websocket,webrtc-datachannels}@^0.6.0(their protocol line moved with polyengine's: polymorph-webcrypto#401, polymorph-websocket#64, polymorph-webrtc-datachannels#168). The relay-ws experiment config takes the same versions as exact pins. Both locks resolve exactly one runtime-family version (0.6.3) and one protocol version (0.3.1).polyengine 0.6.0 (polymorph-components/polyengine#260) removed
CliOptions.passthroughwith no replacement sink, so the exam'sEXAM_GUEST_LOGSknob (live guest stdout/stderr on the console) goes with it; captured text stays reachable through the instance'sstdout()/stderr(). Upstream removed it as "set by nobody" — this repo was the consumer; filing that finding on polyengine.@polymorph/iroh0.5.1 → 0.6.0: the protocol minor bump is breaking under the caret-honest scheme. Publish viajsr-publishafter merge.Gates:
polyengine-setup(--frozen),deno task check(both configs),exam-polyengine— pin drift, identity gate ("one runtime (0.6.3), no raw URLs"), 10/10 scenarios —deno publish --dry-run(@polymorph/iroh@0.6.0),just check.Automerge armed.