sello 0.1.11 → 0.1.13
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/README.md +2 -2
- package/docs/release-checklist.md +2 -0
- package/docs/sdk-quickstart.md +8 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
|
|
1
|
+
|
|
2
2
|
|
|
3
3
|
<h1 align="center">Sello</h1>
|
|
4
4
|
|
|
@@ -158,7 +158,7 @@ Sello does not prove that the agent called every service it should have called,
|
|
|
158
158
|
- [sdks/typescript/examples/mcp-minimal-server.ts](sdks/typescript/examples/mcp-minimal-server.ts): a small MCP-shaped integration.
|
|
159
159
|
- [docs/security-review.md](docs/security-review.md) and [docs/sdk-security-audit.md](docs/sdk-security-audit.md): current review notes.
|
|
160
160
|
|
|
161
|
-
The TypeScript SDK is published on [npm](https://www.npmjs.com/package/sello) and lives in [`sdks/typescript/`](sdks/typescript/). The Python SDK is published on [PyPI](https://pypi.org/project/sello/) and lives in [`sdks/python/`](sdks/python/). Live Rekor proof verification and production identity operations are still future work.
|
|
161
|
+
The TypeScript SDK is published on [npm](https://www.npmjs.com/package/sello) and lives in [`sdks/typescript/`](sdks/typescript/). The Python SDK is published on [PyPI](https://pypi.org/project/sello/) and lives in [`sdks/python/`](sdks/python/). Both SDKs support the same service-side `sello.service()` flow; Python uses the `@receipts.tool(...)` decorator. Live Rekor proof verification and production identity operations are still future work.
|
|
162
162
|
|
|
163
163
|
## Core Terms
|
|
164
164
|
|
|
@@ -54,6 +54,7 @@ python -m twine check dist/*
|
|
|
54
54
|
```
|
|
55
55
|
|
|
56
56
|
The PyPI project uses trusted publishing from `.github/workflows/release.yml`.
|
|
57
|
+
Publishing a GitHub Release for a version tag triggers the PyPI publish job. Use the manual workflow dispatch only when you intentionally want to publish Python without creating a GitHub Release; rerunning the same version is safe because the workflow skips files that already exist on PyPI.
|
|
57
58
|
|
|
58
59
|
## Publish
|
|
59
60
|
|
|
@@ -66,6 +67,7 @@ git push origin main --tags
|
|
|
66
67
|
After publishing:
|
|
67
68
|
|
|
68
69
|
- Confirm `npm view sello version` shows the new version.
|
|
70
|
+
- Publish a GitHub Release for the pushed tag so PyPI trusted publishing runs.
|
|
69
71
|
- Confirm `python -m pip index versions sello` shows the new version after PyPI publishing.
|
|
70
72
|
- Confirm `npx sello --help` works from a clean temp directory.
|
|
71
73
|
- Confirm GitHub Actions passes on `main`.
|
package/docs/sdk-quickstart.md
CHANGED
|
@@ -97,6 +97,14 @@ node --run example:tool
|
|
|
97
97
|
node --run actions
|
|
98
98
|
```
|
|
99
99
|
|
|
100
|
+
Or run the matching Python example:
|
|
101
|
+
|
|
102
|
+
```bash
|
|
103
|
+
python -m pip install ./sdks/python
|
|
104
|
+
python sdks/python/examples/quickstart_tool.py
|
|
105
|
+
npx --yes sello actions
|
|
106
|
+
```
|
|
107
|
+
|
|
100
108
|
For an MCP-shaped `tools/call` boundary, run:
|
|
101
109
|
|
|
102
110
|
```bash
|