You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.22 release gate: publish the managed plugins that are still private #4866
Several families were moved out of core on 0.22 into packages that still declare "private": true. scripts/release-workspace.mjs and scripts/release-publish.mjs pack and publish only public manifests. A 0.22 release cut from this state removes the built-in family and publishes no plugin for it.
The flag is deliberate staging, not an oversight. docs/agents/pull-requests.md requires this order for a new public package: the maintainer publishes an empty placeholder version under a dist-tag other than latest, then configures the npm trusted publisher, and only then a PR removes "private": true.
No package that core's absence hint names (agent-device plugins add @agent-device/<name>) is private at the release commit.
A check in the release path fails when an install hint names a package that the release would not publish. Without it, this gap can return for the next extracted family.
The issue requests pre-release publishing work: changing private manifests to public, following a documented placeholder/trusted-publisher process, and adding a release-path check so plugin install hints cannot name unpublished packages.
Status after #4918 (merged as 78ca7b4): nightly 0.22.0-nightly-0-22.20261121.235 (run 44939433597) published the core and every managed plugin through the release workflow with npm trusted publishing.
Clean-consumer check (fresh project, isolated AGENT_DEVICE_HOME/AGENT_DEVICE_STATE_DIR, npm install agent-device@0.22.0-nightly-0-22.20261121.235): agent-device plugins add @agent-device/<name>@nightly-0.22 installed web, vega, harmonyos, linux, maestro and replay at 0.22.0-nightly-0-22.20261121.235, and plugins list reports each as compatible. devices --platform web then answered from the installed web plugin (agent-browser-chrome, booted).
Remaining before this issue closes: @agent-device/limrun flips in #4846 (its install hint would otherwise fail the new release check), and @agent-device/macos lands with #4675. Placeholders and trusted publishers exist for both.
Activity
apex-sentinel-staging commentedon Nov 20, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue requests pre-release publishing work: changing private manifests to public, following a documented placeholder/trusted-publisher process, and adding a release-path check so plugin install hints cannot name unpublished packages.
chore(gates): fail a release whose install hint names an unpublished …
chore(release): publish the managed platform plugins (#4918)
thymikee commentedon Nov 21, 2026
Status after #4918 (merged as 78ca7b4): nightly
0.22.0-nightly-0-22.20261121.235(run 44939433597) published the core and every managed plugin through the release workflow with npm trusted publishing.Clean-consumer check (fresh project, isolated
AGENT_DEVICE_HOME/AGENT_DEVICE_STATE_DIR,npm install agent-device@0.22.0-nightly-0-22.20261121.235):agent-device plugins add @agent-device/<name>@nightly-0.22installed web, vega, harmonyos, linux, maestro and replay at0.22.0-nightly-0-22.20261121.235, andplugins listreports each as compatible.devices --platform webthen answered from the installed web plugin (agent-browser-chrome, booted).Remaining before this issue closes:
@agent-device/limrunflips in #4846 (its install hint would otherwise fail the new release check), and@agent-device/macoslands with #4675. Placeholders and trusted publishers exist for both.chore(release): publish the managed platform plugins (#4918)