Release v0.0.50 - #295
Release v0.0.50#295
Conversation
…ygiene guarantees Every strix retest found a credential/output-hygiene fix correct on main but still present in the installed binary — a release-publishing gap. New ci/release-smoke.weir runs the promises against a binary (URL userinfo redaction, bounded parse/decode errors, deep-value no-crash) via the transport-error path and file-run rendering — no server, no tty, portable. release.yml's build job self-tests each freshly-built artifact before upload, so a regressed promise can't reach 'released'. Verified: fixed binary 3/3, v0.0.47 fails at check 1 (userinfo verbatim, exit 1).
…al pair
Sibling objects with different keys whose values only coincidentally agreed
in an early pair (a k8s securityContext: bool field, then int two elements
later) made the pairwise merge commit to seq<string * bool>, and a later
'from json' rejected the int ('expected bool, got Number'). Defer the
open-map verdict from the pairwise mergeObjs to a post-merge openMaps pass
over the fully-merged shape, where value uniformity is judged across every
sibling: mixed values stay a typed record; genuinely uniform data-keyed
objects (ConfigMap data) still draft an open mapping. The now-dead IMap
absorb arms in mergeTwo are removed.
…suggest within tmp)
Strix Security ReviewWarning This pull request has 7 commits after the last Strix review ( No security issues found. Review summaryReviewed all 20 changed files in this release PR, focusing on the new The A targeted Updated for Reviewed by Strix |
…refusal arm (avoid an FS0193 compiler ICE on the CI SDK)
… the large Builtins module
2defa47 to
a325502
Compare
d66eb29 to
f9f1a0e
Compare
No description provided.