glaze 7.1.0

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

Details

release notes

# Glaze v7.1.0
This release focuses on YAML maturity, networking reliability, container/generic behavior, and platform compatibility.

[!IMPORTANT]

glz::generic now supports different underlying map types, but now defaults to a faster, ordered map, which preserves insertion order rather than sorting lexicographically. This ensures proper round tripping for unsorted JSON objects. See documentation for more details: https://stephenberry.github.io/glaze/generic-json

YAML Maturity
YAML support received major hardening and coverage improvements, including parser correctness, conformance, roundtrip behavior, and generic integration.
Related pull requests: #2289, #2293, #2297, #2298, #2300, #2302, #2305, #2317, #2324, #2335.
Networking Improvements
HTTP/WebSocket behavior was improved across TLS support, handshake compatibility, CPU efficiency, and server internals.
Related pull requests: #2260, #2284, #2292, #2321, #2322, #2323.
Generic and Container Behavior
Runtime generic behavior and ordered container support were improved, including insertion-order preservation and additional integer generic access support.
Related pull requests: #2318, #2325, #2334.
Platform and Toolchain Compatibility
Compatibility and CI coverage improved for MSVC and ARM targets, along with sanitizer/toolchain robustness fixes.
Related pull requests: #2273, #2288, #2303, #2304, #2309, #2336, #2337.
Core Improvements and Fixes
Core quality improvements include SIMD/reflection work and correctness fixes around key handling and string conversion behavior.
Related pull requests: #2270, #2281, #2290, #2329.
Full Changelog

stephenberry/glaze@v7.0.2...v7.1.0

View the full release notes at https://github.com/stephenberry/glaze/releases/tag/v7.1.0.

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.