@extension.dev/deploy 0.2.4 → 0.3.0

package/CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+## 0.2.5
+
+Current release. Earlier history is tracked in the source monorepo; entries
+below summarize the package as shipped.
+
+- `extension-deploy` CLI and `deploy()` library API for Chrome Web Store,
+  Firefox AMO, and Edge Partner Center submissions.
+- Draft and unlisted submission modes for non-destructive store testing.
+- Dry-run mode, config file + environment variable credential resolution,
+  zod validation schemas exported for consumers.
+- Watch mode for resubmission flows.

package/README.md

@@ -97,6 +97,11 @@ Run `extension-deploy --help` for the full list of flags.
 | `--firefox-jwt-secret <secret>` | `FIREFOX_JWT_SECRET`   | AMO JWT secret                             |
 | `--firefox-channel <channel>`   | `FIREFOX_CHANNEL`      | `"listed"` or `"unlisted"`                 |
 
+`--firefox-extension-id` is optional for an **unlisted first submission**: with no
+GUID and `--firefox-channel unlisted`, a new add-on is created and AMO assigns the
+GUID. Provide the GUID to push a new version to an existing add-on. Listed
+submissions always require an existing GUID.
+
 ### Edge Partner Center
 
 | Flag                        | Env var                   | Description                    |
@@ -122,6 +127,22 @@ CHROME_CLIENT_SECRET=GOCSPX-xxx
 CHROME_REFRESH_TOKEN=1//0xxx
 ```
 
+## Drafts and deletion
+
+This package only uploads and publishes. It intentionally has **no delete or
+discard command**: it is meant to run in CI, where the credentials it carries
+should not be able to destroy a listing.
+
+If you upload a draft (Chrome `--chrome-skip-submit-review`, Edge
+`--edge-skip-submit-review`) you do not need to clean it up:
+
+- Chrome and Edge drafts are **private** (never shipped to users) and are
+  **overwritten by your next upload**. Neither store exposes a draft-discard or
+  item-delete API; deleting an item is a dashboard-only action.
+- Firefox add-ons can be deleted through the AMO Developer Hub. A throwaway
+  unlisted add-on created for testing is best **reused** (push new versions to
+  the same GUID) rather than recreated each run.
+
 ## Library usage
 
 ```ts
@@ -165,7 +186,7 @@ if (!result.success) {
 
 ### `deploy(config): Promise<DeployResult>`
 
-Deploys to all configured stores in parallel. Only stores with a config object are included — omit a store to skip it.
+Deploys to all configured stores in parallel. Only stores with a config object are included; omit a store to skip it.
 
 **`DeployConfig`**
 
@@ -262,6 +283,18 @@ What the workflow does:
 5. Pushes the commit and tag
 6. Publishes the package to npm
 
+## The extension.dev open source stack
+
+| Package | Use it to |
+| --- | --- |
+| [`@extension.dev/mcp`](https://github.com/extensiondev/mcp) | Give AI agents tools to build, run, and debug extensions |
+| [`@extension.dev/skill`](https://github.com/extensiondev/skill) | Teach agents the cross-browser rules and silent-failure gotchas |
+| [`@extension.dev/artifact-integrity`](https://github.com/extensiondev/artifact-integrity) | Gate releases on artifact verification |
+| [`@extension.dev/compiler`](https://github.com/extensiondev/compiler) | Build extensions in the browser with esbuild-wasm |
+| [`@extension.dev/core`](https://github.com/extensiondev/core) | Authenticate and publish to the extension.dev platform |
+
+All of it rides on [Extension.js](https://github.com/extension-js/extension.js), the open-source cross-browser extension framework.
+
 ## License
 
 MIT