afterpack 0.2.5 → 0.2.7

package/README.md

@@ -163,7 +163,8 @@ and sends everything else to stderr. Use it in CI and scripts. `verify` and `aud
 Without a key, AfterPack runs on your machine with the full pipeline at any preset. Set
 [`AFTERPACK_KEY`][key] in your environment (or [`key`][key] in `afterpack.json`) and the same
 command builds in AfterPack's cloud instead, which adds two hardening transforms you can turn on:
-self-integrity (anti-tamper) and comparison hardening. If the cloud cannot be reached, the run
+self-integrity, which detects edits to its own check table only, not edits
+elsewhere in your code, and comparison hardening. If the cloud cannot be reached, the run
 fails; it never falls back to a local build. Never commit the key. See [AfterPack
 Pro](https://www.afterpack.dev/docs/pro).
 

package/SKILL.md

@@ -201,7 +201,8 @@ Lists are sorted and there are no timestamps, so two runs of one build give iden
 
 Without a key, builds run locally with the full pipeline at any preset. With a Pro key, the same
 command builds in AfterPack's cloud instead, which adds two hardening transforms you can turn on:
-self-integrity (anti-tamper) and comparison hardening.
+self-integrity, which detects edits to its own check table only, not edits
+elsewhere in your code, and comparison hardening.
 
 - Set it as `AFTERPACK_KEY` in the environment (a CI secret), or [`key`][key] in an uncommitted
   `afterpack.json`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "afterpack",
-  "version": "0.2.5",
+  "version": "0.2.7",
   "description": "AfterPack CLI: obfuscate the JavaScript in any build output, verify a build before deploy, and scan a live site",
   "type": "module",
   "bin": {
@@ -14,8 +14,8 @@
     "dist"
   ],
   "dependencies": {
-    "@afterpack/core": "~0.2.6",
-    "@afterpack/integration-utils": "0.2.5"
+    "@afterpack/core": "~0.2.8",
+    "@afterpack/integration-utils": "0.2.7"
   },
   "devDependencies": {
     "@biomejs/biome": "2.4.4",