Repository navigation
Prepare combined Swift-JSON 1.7.0 release candidate - #70
Merged
Merged
Conversation
Integrates the reviewed five-file Transform documentary checkpoint 84cb253ee68578385969a047780e02f752e78f42 by exact content. Preserves all runtime/API semantics. Candidate metadata is 1.7.0; G4/P4 and final-source qualification remain explicit gates. No merge, tag or publication follows.
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
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.
Prepare a single combined Swift-JSON 1.7.0 candidate from main
15aa7e4: twelve libraries plus swift-json, thirteen DocC catalogs and the same 1,500 authored declarations. This 17-file diff updates version/site metadata, the exact CLI version regression, deterministic source identity, release notes/checklist and roadmap, and integrates Transform A's exact five-file documentary checkpoint84cb253. No engine, package manifest, harness, fixture, metric or public signature changed.Frozen head:
32e9726fa97132fb7cf0439af3dcec972aea6666; tree:c914b8914c9130a3a07a3ed82fb41dde33c37402. Stable 1.6.1 and historical RC6fe8067remain separate and unchanged.Validation: all eight fresh Native/Linux jobs passed on this source. The twelve actual lane records preserve Native 975 / Linux 959 functions,390 parameters, ASan, TSan 60/59, strict/lifetime, ownership/compiler, consumers and independent conformance gates. The full 58-command Git-free native lane passed; its 2,159,435-byte archive exactly matches the local deterministic source (SHA-256
6878714a6ea728ebdf00e386ae062064345c634f0d4670eb9ef255fde4db519e). Fresh compiler graphs preserve all 1,500 declarations;13 compiled catalogs/5027 files document all 1,500;16 README fences and10962 local links passed. Independent remote-revision Debug/Release consumers passed12 commands, with all 1,507 checkout hashes verified.Portable qualification is explicitly scoped: the allowed unchanged-input rule maps209 public-library and 317 WASI test/policy inputs to actual prior 82-command WASI receipts; SDK reuse remains its precise four roots/ten dependency targets/157 compiled inputs. New 19-command probes produced 12 real Debug/Release metadata objects under strict memory for iPhoneOS, Simulator and pinned WASI. Full-refresh local attempts hit ENOSPC and remain failures; no new whole-root/device/WASI-sanitizer/CLI-runtime result is claimed. Independent Transform review checked those boundaries and found no blocker.
Performance: maintainer accepted a source-specific P4 exception for
32e9726. Navigation G4 remains HOLD, zero accepted controlled timing samples; 44/150 and 119/150 remain separate partial windows. No speed, throughput, allocation-efficiency or RSS claim, and no other gate waiver. The 10% trigger and historical streaming disposition remain.Actual source/DocC/public qualification/checksum assets are prepared locally and privacy-reviewed. This PR remains draft for owner review. Protected merge, tag, GitHub release creation and publication require separate instructions; nothing was uploaded as release assets. Public store/follow, batches, persistence and wider retrieval remain deferred.