@camstack/develop 0.1.33 → 0.1.34

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/develop",
3
- "version": "0.1.33",
3
+ "version": "0.1.34",
4
4
  "description": "CamStack developer tooling — catalogue, scaffold, validate, and example lookup shared by the CLI and MCP server.",
5
5
  "keywords": [
6
6
  "camstack",
@@ -226,10 +226,12 @@ Traps, each of which has cost a session:
226
226
  skew, roll the enablement back.
227
227
  - **Repeated rapid deploys of media addons** (stream broker, providers)
228
228
  degrade the hub. One deploy, then verify; a restart only if needed.
229
- - **The hub auto-updater** applies newly published npm versions on its
230
- schedule and can replace a CLI-deployed build whose version differs; deploy
231
- after the version-bump commit, and check `addons.setAddonAutoUpdate` for
232
- framework packages.
229
+ - **The hub auto-updater** follows registry `latest` in either direction
230
+ (D942) when the addon's channel allows it, and replaces a CLI-deployed
231
+ build whose version is not that tag. An agent follows the **hub's**
232
+ installed version, not npm. The framework row is still strictly newer
233
+ (D175). Deploy after the version-bump commit if the deploy must survive
234
+ the next sweep.
233
235
  - **admin-ui** deploys need no hub restart, but a browser keeps the old PWA
234
236
  bundle until a hard reload; a blank page with a "MIME type text/html" module
235
237
  error is a stale service worker.