release: 2026.8.18.1

The date-based convention labels a release by the day it goes out, and the
previous one (2026.8.17.1) is already published — so this is the first release of
the 18th, not a second one of the 17th.

Two version sites move (mcpp.toml and src/version.cppm; fingerprint.cppm derives
from the latter), the CHANGELOG's Unreleased section becomes the release heading,
and the docs' "until mcpp <version>" notes name the release that actually ships
those changes. The `XLINGS_VERSION: '2026.8.17.2'` entries under .github/ are the
xlings pin, which happens to carry the same digits and must not move with this.

`check_version_pins.sh`: building 2026.8.18.1, bootstrapping from 2026.8.17.1,
xlings pins all at 2026.8.17.2.

Author: speak-agent

CHANGELOG.md

@@ -3,7 +3,7 @@
 > 本文件追踪 `mcpp-community/mcpp` 公开仓的版本演进。
 > 格式参考 [Keep a Changelog](https://keepachangelog.com/zh-CN/1.1.0/)。
 
-## [Unreleased]
+## [2026.8.18.1] — 2026-08-18
 
 ### 新增
 

docs/05-mcpp-toml.md

@@ -156,7 +156,7 @@ the package/feature boundary, not on an individual target.
 > **`sources = []` is not the same as omitting `sources`.** An absent key
 > selects the default glob; an explicitly empty list means *compile nothing*,
 > which is what a header-only distribution package needs to say. Until
-> mcpp 2026.8.17.2 the two were byte-identical, so there was no spelling for
+> mcpp 2026.8.18.1 the two were byte-identical, so there was no spelling for
 > "nothing" and any file left under `src/` was swept in.
 
 ```toml

docs/12-binary-distribution.md

@@ -225,7 +225,7 @@ target is known, a fat package cross-compiles correctly with no index-side or
 installer-side support at all.
 
 > The blocks are `cfg(...)` and never a bare `[target.'<triple>']` key. Before
-> mcpp 2026.8.17.2 the bare form was inert without an explicit `--target`, so a
+> mcpp 2026.8.18.1 the bare form was inert without an explicit `--target`, so a
 > package using it would work in CI and silently drop its flags on a
 > developer's machine. mcpp generates the spelling that means the same thing on
 > every client.
@@ -335,7 +335,7 @@ warning: secret.cppm is an implementation partition, and the published interface
          reaches it — so its SOURCE is being published.
 ```
 
-> Until mcpp 2026.8.17.2 the scanner recorded `module M:part;` as *requiring*
+> Until mcpp 2026.8.18.1 the scanner recorded `module M:part;` as *requiring*
 > `M:part` and providing nothing, so a file required its own name and the graph
 > held no edge from the unit importing a partition to the unit defining it.
 > Build order was unconstrained: GCC and macOS clang recovered through their own
@@ -355,7 +355,7 @@ warning: secret.cppm provides a module PARTITION and mcpp cannot tell which kind
          whether the declaration carries `export`, …
 ```
 
-> Until 2026.8.17.2 that arrived as "it is an interface" — the answer that
+> Until 2026.8.18.1 that arrived as "it is an interface" — the answer that
 > produces **no** warning — so an implementation partition declared that way was
 > published in silence. Publishing too few sources fails the consumer's compile
 > and names the module; publishing too many ships private source and nothing

docs/zh/12-binary-distribution.md

@@ -205,7 +205,7 @@ ldflags = ["-Llib/x86_64-linux-musl", "-lmathkit"]
 胖包的交叉编译天然正确,**不需要索引侧或安装侧做任何支持**。
 
 > 这些块是 `cfg(...)`,绝不是裸的 `[target.'<三元组>']` 键。
-> 在 mcpp 2026.8.17.2 之前,裸三元组在没有显式 `--target` 时是失效的 ——
+> 在 mcpp 2026.8.18.1 之前,裸三元组在没有显式 `--target` 时是失效的 ——
 > 用它的包会在 CI 里正常、在开发者机器上静默丢掉 flag。
 > mcpp 生成的是在**所有**客户端上含义一致的那种写法。
 
@@ -296,7 +296,7 @@ warning: secret.cppm is an implementation partition, and the published interface
          reaches it — so its SOURCE is being published.
 ```
 
-> 在 mcpp 2026.8.17.2 之前,扫描器把 `module M:part;` 记成**「requires `M:part`、
+> 在 mcpp 2026.8.18.1 之前,扫描器把 `module M:part;` 记成**「requires `M:part`、
 > provides 空」** —— 一个文件 requires 自己的名字,于是图里**没有**从「import 分区
 > 的单元」到「定义分区的单元」的边,构建顺序无约束:GCC 与 macOS clang 靠各自的
 > 依赖扫描兜住了,**Windows clang 以 `failed to read compiled module` 失败**。
@@ -314,7 +314,7 @@ warning: secret.cppm provides a module PARTITION and mcpp cannot tell which kind
          whether the declaration carries `export`, …
 ```
 
-> 在 2026.8.17.2 之前,这种情况以「它是接口」到达 —— 那个**不产生任何警告**的答案 ——
+> 在 2026.8.18.1 之前,这种情况以「它是接口」到达 —— 那个**不产生任何警告**的答案 ——
 > 于是这样声明的实现分区被一声不响地发布了。**发布得太少**会让消费者编译失败并点名
 > 模块;**发布得太多**会把私有源码发出去,而什么都不会失败。未知必须出声。
 

mcpp.toml

@@ -1,6 +1,6 @@
 [package]
 name        = "mcpp"
-version = "2026.8.17.2"
+version = "2026.8.18.1"
 description = "Modern C++ build & package management tool"
 license     = "Apache-2.0"
 authors     = ["mcpp-community"]

src/version.cppm

@@ -31,6 +31,6 @@ import std;
 
 export namespace mcpp {
 
-inline constexpr std::string_view MCPP_VERSION = "2026.8.17.2";
+inline constexpr std::string_view MCPP_VERSION = "2026.8.18.1";
 
 } // namespace mcpp