deploy.

2026-09-13 19:45:24 +08:00
parent 397a7a8cc4
commit 2db889ad89
58 changed files with 3526 additions and 213 deletions
@@ -109,8 +109,9 @@ own, so the set is quoted as <code>3.1.175.&lt;patch&gt;</code> after its HiNc p
 it publish under their own frozen builds — looking on the feed for every package at <code>3.1.175.x</code>
 finds only HiNc. A reference left on that set receives correctness fixes for it and none of the
 capability on this page. The 3.1 builds above 3.1.175 were never published as a release set —
-which is why the release note carries one 3.2 entry where it might have carried a dozen: for a
-caller moving off 3.1.175, they were never separate releases.</li>
+which is why <strong>3.2.7</strong> is the first numbered 3.2 drop and absorbs what a caller moving off
+3.1.175 has not seen as a published set. Later 3.2 builds are incremental, the same way
+3.1.175 / 3.1.173 / … were.</li>
 </ul>

 </article>