Re-vendor serialize @ v1.6.0 (was 1.5.0); yojimbo 1.9.1 (mas-bandwidt…

…h#327)

Updates the vendored serialize.h to the serialize v1.6.0 release (4e34df6):
fixed-point + 128-bit integers, the compile-time const-params surface
(C++14-gated, so the C++03 consumer leg is preserved), and the restrict-writer
optimization. yojimbo's own API is unchanged, so this is a patch bump; both
version sites moved together for the version-consistency gate.

Merge pull request mas-bandwidth#325 from mas-bandwidth/system-tlsf

YOJIMBO_SYSTEM_TLSF: build against a system-installed tlsf

yojimbo 1.8.2: re-vendor netcode 1.4.3 (mas-bandwidth#323)

* yojimbo 1.8.2: re-vendor netcode 1.4.3

Picks up netcode's mas-bandwidth#173 fix, which matters here specifically: yojimbo's
Client::GenerateInsecureConnectToken calls netcode_generate_connect_token directly,
so before this the out-of-range path in yojimbo was unguarded twice over -- its own
assert, and then netcode's assert underneath it. netcode now returns NETCODE_ERROR
at runtime instead.

sodium/ is untouched and verified byte-identical to netcode's, so the parity
workflow is unaffected.

Version is a PATCH bump even though mas-bandwidth#320 changes classification results for
addresses previously reported as global unicast. The old behaviour was a defect
rather than a contract -- nothing could correctly depend on ff02::1 being global
unicast -- so semver puts this at patch. Flagged in the release notes regardless,
because "it is a bug fix" and "it is a behaviour change" are both true.

Full test suite verified locally against the re-vendored netcode before this
commit, including the new test_address_classification.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* yojimbo 1.8.2: bump yojimbo_config.h too

The version lives in two places and I bumped only CMakeLists.txt. The version
consistency check caught it, which is exactly what it is for -- one truth, two
copies, and a reader that refuses to let them disagree.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings) (m…

…as-bandwidth#316)

* yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings)

* yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings)

* yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings)

* yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings)

* yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings)

* yojimbo 1.8.1: re-vendor netcode 1.4.2 (libsodium 1.0.22 hardenings)

yojimbo 1.8.0 (mas-bandwidth#315)

* vendor: sync dependency copies to the 2026-07-25 releases

* vendor: sync dependency copies to the 2026-07-25 releases

* vendor: sync dependency copies to the 2026-07-25 releases

* vendor: sync dependency copies to the 2026-07-25 releases

* docs: drop the Doxygen block orphaned by the serialize_ack_relative removal

* yojimbo 1.8.0

* yojimbo 1.8.0

Sync vendored version strings: reliable 1.3.5, serialize 1.4.4

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Merge pull request mas-bandwidth#305 from mas-bandwidth/bsd-support

Add BSD support (OpenBSD, FreeBSD)

Bump version to 1.6.2

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Merge pull request mas-bandwidth#302 from mas-bandwidth/fix/self-cont…

…ained-libyojimbo-install

Fold tlsf into libyojimbo.a for the system-deps install

Merge pull request mas-bandwidth#300 from mas-bandwidth/vendor/serial…

…ize-1.4.3

Update vendored serialize v1.4.3 + reliable v1.3.2; fix write-buffer alignment