forgeqe-cli 2.2.6__tar.gz → 2.2.7__tar.gz

{forgeqe_cli-2.2.6/py/forgeqe_cli.egg-info → forgeqe_cli-2.2.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: forgeqe-cli
-Version: 2.2.6
+Version: 2.2.7
 Summary: pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)
 Author: CLI-Agents
 License: MIT
@@ -59,6 +59,22 @@ One-shot release (same version on both registries; assumes `npm` and `twine` are
 ./scripts/publish.sh --dry-run # pack only
 ```
 
+Or let CI publish: merge a version bump (the same version in `package.json`, `pyproject.toml` and
+`py/forgeqe_cli/__init__.py`) to `main`, and [`forgeqe-release.yml`](../.github/workflows/forgeqe-release.yml) runs the
+release tests and publishes it to npm and PyPI. It publishes only a version newer than the one each registry has. Run it
+by hand from the Actions tab for a dry run.
+
+It needs no token: both registries trust the workflow (trusted publishing). Set that up once, as the package owner:
+
+```bash
+npm install -g npm@^11.15.0 && npm login
+npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/cli-agents --allow-publish
+```
+
+and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
+`cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
+expires, so do it just before the first release.
+
 ## Privacy
 
 ForgeQE sends no telemetry and turns it off in everything it starts:

forgeqe_cli-2.2.6/PKG-INFO → forgeqe_cli-2.2.7/README.md

@@ -1,18 +1,3 @@
-Metadata-Version: 2.4
-Name: forgeqe-cli
-Version: 2.2.6
-Summary: pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)
-Author: CLI-Agents
-License: MIT
-Keywords: forgeqe,browser,agent,cli,opentui
-Requires-Python: >=3.9
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: truststore==0.10.4; python_version >= "3.10"
-Provides-Extra: dev
-Requires-Dist: pytest>=8.0; extra == "dev"
-Dynamic: license-file
-
 # ForgeQE
 
 Test agent CLI for web, Windows desktop and mobile apps. Say what you want in plain language: a goal to carry out in a browser, a Windows app or an Android or iOS app, test cases to run from Jira, Azure DevOps, Xray or a file, a test to write, or a CI pipeline to set up. ForgeQE's agent works out what that needs and calls ForgeQE's tools. The ForgeQE engine drives Chrome locally, or BrowserStack and TestMu AI/LambdaTest through their Chrome DevTools Protocol (CDP) endpoints, and a run that passes becomes a test in your repo's own language and framework, written by **Scribe**, ForgeQE's coding agent. Skills (`SKILL.md` folders, built in or in `.forgeqe/skills`) teach the agents your repo's conventions and the apps you test.
@@ -59,6 +44,22 @@ One-shot release (same version on both registries; assumes `npm` and `twine` are
 ./scripts/publish.sh --dry-run # pack only
 ```
 
+Or let CI publish: merge a version bump (the same version in `package.json`, `pyproject.toml` and
+`py/forgeqe_cli/__init__.py`) to `main`, and [`forgeqe-release.yml`](../.github/workflows/forgeqe-release.yml) runs the
+release tests and publishes it to npm and PyPI. It publishes only a version newer than the one each registry has. Run it
+by hand from the Actions tab for a dry run.
+
+It needs no token: both registries trust the workflow (trusted publishing). Set that up once, as the package owner:
+
+```bash
+npm install -g npm@^11.15.0 && npm login
+npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/cli-agents --allow-publish
+```
+
+and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
+`cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
+expires, so do it just before the first release.
+
 ## Privacy
 
 ForgeQE sends no telemetry and turns it off in everything it starts:

{forgeqe_cli-2.2.6 → forgeqe_cli-2.2.7}/py/forgeqe_cli/__init__.py

@@ -4,4 +4,4 @@ The agent itself is the npm package ``@capagents/forgeqe`` (OpenTUI + Bun).
 This distribution only puts a ``forgeqe`` command on PATH.
 """
 
-__version__ = "2.2.6"
+__version__ = "2.2.7"

forgeqe_cli-2.2.6/README.md → forgeqe_cli-2.2.7/py/forgeqe_cli.egg-info/PKG-INFO

@@ -1,3 +1,18 @@
+Metadata-Version: 2.4
+Name: forgeqe-cli
+Version: 2.2.7
+Summary: pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)
+Author: CLI-Agents
+License: MIT
+Keywords: forgeqe,browser,agent,cli,opentui
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: truststore==0.10.4; python_version >= "3.10"
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Dynamic: license-file
+
 # ForgeQE
 
 Test agent CLI for web, Windows desktop and mobile apps. Say what you want in plain language: a goal to carry out in a browser, a Windows app or an Android or iOS app, test cases to run from Jira, Azure DevOps, Xray or a file, a test to write, or a CI pipeline to set up. ForgeQE's agent works out what that needs and calls ForgeQE's tools. The ForgeQE engine drives Chrome locally, or BrowserStack and TestMu AI/LambdaTest through their Chrome DevTools Protocol (CDP) endpoints, and a run that passes becomes a test in your repo's own language and framework, written by **Scribe**, ForgeQE's coding agent. Skills (`SKILL.md` folders, built in or in `.forgeqe/skills`) teach the agents your repo's conventions and the apps you test.
@@ -44,6 +59,22 @@ One-shot release (same version on both registries; assumes `npm` and `twine` are
 ./scripts/publish.sh --dry-run # pack only
 ```
 
+Or let CI publish: merge a version bump (the same version in `package.json`, `pyproject.toml` and
+`py/forgeqe_cli/__init__.py`) to `main`, and [`forgeqe-release.yml`](../.github/workflows/forgeqe-release.yml) runs the
+release tests and publishes it to npm and PyPI. It publishes only a version newer than the one each registry has. Run it
+by hand from the Actions tab for a dry run.
+
+It needs no token: both registries trust the workflow (trusted publishing). Set that up once, as the package owner:
+
+```bash
+npm install -g npm@^11.15.0 && npm login
+npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/cli-agents --allow-publish
+```
+
+and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
+`cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
+expires, so do it just before the first release.
+
 ## Privacy
 
 ForgeQE sends no telemetry and turns it off in everything it starts:

{forgeqe_cli-2.2.6 → forgeqe_cli-2.2.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "forgeqe-cli"
-version = "2.2.6"
+version = "2.2.7"
 description = "pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)"
 readme = "README.md"
 requires-python = ">=3.9"