cli-releases: v2.16.1 artifacts (#608)

Release artifacts generated by CI for CLI v2.16.1.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: caffeine-ci-bot[bot]

cli-releases/releases.json

@@ -1,6 +1,6 @@
 {
   "tags": {
-    "latest": "2.16.0"
+    "latest": "2.16.1"
   },
   "versions": {
     "0.41.0": {
@@ -496,6 +496,14 @@
       "commitHash": "466636a99803946e996609153917ce7f0d52e953",
       "url": "https://cli.mops.one/versions/2.16.0.tgz",
       "hash": "79fee9e8f0deb4350989a54a9a7c0575466198380697a45d2ce88b09e76fc27f"
+    },
+    "2.16.1": {
+      "time": 1782832782218,
+      "size": 2412866,
+      "relseaseNotes": "* Fix `mops bench` crashing on moc 0.15+ with the default `--gc copying`: `--copying-gc` is rejected under enhanced orthogonal persistence, which became the default persistence mode in 2.16.0. The default GC is now `incremental` (moc's default and the only collector available under EOP). Selecting a legacy collector (`copying`, `compacting`, `generational`) now implies `--legacy-persistence`, since moc only accepts them there.\n* `mops build`, `mops check`, `mops generate`, and `mops check-stable` now tunnel `moc`'s exit code instead of always exiting `1`. moc exits `2` on a compiler crash (uncaught internal error) versus `1` for normal user errors (type/compile errors, stable-compat mismatch, bad args), so CI and scripts can now distinguish \"file a Motoko bug\" from \"fix your code\" via `$?`. `mops test` likewise exits `2` when a `moc` process crashes during a test run, instead of reporting it as an ordinary test failure.\n",
+      "commitHash": "4bccdc13b512048f41b3296c3590b776c1836fe1",
+      "url": "https://cli.mops.one/versions/2.16.1.tgz",
+      "hash": "35ebb4899e777367c55fd526ebfa2618ba6c390698fc72cd239533b76cd6e188"
     }
   }
 }

cli-releases/tags/latest

@@ -1 +1 @@
-2.16.0
+2.16.1