Skip to content

0.22 release gate: publish the managed plugins that are still private #4866

Open

Description

@thymikee

Purpose

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.

Packages

Package Directory State on 0.22
@agent-device/web packages/platform-web private (merged in #4792)
@agent-device/vega packages/platform-vega private (merged in #4828)
@agent-device/harmonyos packages/platform-harmonyos private (PR #4857)
@agent-device/limrun packages/provider-limrun private (PR #4846)
@agent-device/maestro packages/maestro private

Already public: @agent-device/browserstack, @agent-device/aws-device-farm. Add Linux desktop (#4676) and macOS desktop (#4675) here when they land.

Required before the 0.22 release

For each package above:

  1. Maintainer: publish the placeholder and configure the trusted publisher.
  2. One PR: remove "private": true, and confirm the release scripts pack and publish it.
  3. Verify from a clean consumer: agent-device plugins add <package>@<0.22 version> installs, selects and activates it, as was done for BrowserStack and AWS Device Farm (0.22: ship a mobile-first, plugin-free core and measure size reduction #4591 status of 2026-11-18).

Completion conditions

  • 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.

Activity

  1. added this to the 0.22 - lean core milestone on Nov 20, 2026
  2. apex-sentinel-staging commented on Nov 20, 2026

    @apex-sentinel-staging

    Apex Sentinel · Issue review

    Suggested label: feature

    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.

  3. thymikee commented on Nov 21, 2026

    @thymikee
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions