Published 1.9.0 introduced these workflows; main continues from it.
Run python3 Scripts/ci.py --lane structural-workflows for exact Debug/Release
behavior, preserved store cases and public compiler/consumer checks. M2 adds
--lane structural-acceptance and --lane structural-acceptance-safety for exact
public cross-product cases, deterministic capacity observations and their safety
checks. These extend the existing gates. Run
--lane structural-workflows-safety for scoped ASan, shared-state TSan and strict
memory checks; complete native/Linux/docs/WASI gates still apply before release.
Do not infer a pass when storage or an actual supported runtime is unavailable.
Choose the source line deliberately: maintenance changes use the 1.6 line; new capabilities target development. This checkout is unreleased 1.7.0-dev consolidation source; preserve the reviewed component APIs/algorithms and qualify every combined source. Keep the lines' API inventories separate and map applicable maintenance corrections forward by content/commit, without assuming a squashed maintenance tip is an ancestor of main. See the release-line matrix.
Open a focused pull request against the appropriate source line (release/1.6
for maintenance, main for development) at
ThorFuchs/Swift-JSON. Maintainer:
@ThorFuchs. Contributions require Swift 6.4+,
Swift language mode 6 and macOS/SDK 27+ for native validation.
Read AGENTS.md and the relevant behavior contracts. Describe the observable change, its reason, tests run and material limitations. Use Swift Testing for behavior, adversarial inputs and boundaries. Keep a minimal failing input and deterministic seed for parser, number and regex regressions. Exercise public consumers in addition to tests using internal access.
Run the affected lanes from the root:
python3 Scripts/ci.py --lane native
python3 Scripts/ci.py --lane safety
python3 Scripts/ci.py --lane docsFor Linux changes also run python3 Scripts/ci.py --lane linux and
--lane linux-safety on an actual Swift 6.4+ Ubuntu 24.04/glibc runtime.
Linux results supplement the Apple gates; see the platform contract.
Keep APIs neutral and exact, budgets cumulative and mutable state invocation-owned. Do not add platforms, permissive parsing, online schema resolution, fallback engines or runtime dependencies without an explicit design review. Benchmark and fixture tools use separate packages. Preserve upstream pins and licenses when adapting code. Original contributions use Apache-2.0.
Use Issues for defects and support, and SECURITY.md for private reports. Do not submit secrets or private application fixtures. See SUPPORT.md for the maintenance policy.
Public API changes need useful Swift documentation comments and a focused guide when semantics span multiple calls. README Swift examples must match their compiled consumer. See documentation tooling for coverage checks, compiled examples and native DocC builds.
The optional consumer developer kit is separate from these contributor instructions. Keep its canonical skill, pinned public recipes and standalone/plugin distributions in sync through the focused acceptance harness; independent review precedes merge and distribution.