Repository navigation
release: v0.3.0, published to npm and PyPI from a tag - #49
Merged
Merged
Conversation
The Python package has never been published, so this is what its PyPI page and its files need: - The sdist holds the package source, the README, the license and pyproject.toml. The tests and the bench stay out: they read fixtures and TypeScript sources from the repo around python/, so they cannot run from an unpacked sdist. - The README's links are absolute. PyPI renders the README on its own page, where a link such as ../docs/reference.md leads nowhere. - Documentation and Changelog links in the project URLs, and classifiers for the operating system, Python 3 only and the topic. Co-Authored-By: Claude <noreply@anthropic.com>
Sets the version to 0.3.0 in the five places it is written: package.json, python/pyproject.toml, python/uv.lock, the plugin manifest, and the version the MCP server reports, which was a literal '0.2.0' in two places in src/server/http.ts and is now one constant in src/internal/version.ts. scripts/check-version.mjs fails when those five disagree, and when a tag is given, when the tag does not name the version. `pnpm check` runs it. CHANGELOG.md is new. Its 0.3.0 entry covers everything merged since 0.2.0 reached npm: the Python package, folded notices, observation time, per-event quiet durations, serial intake, accumulating continuation, separate event limits, and the two `attend serve` wake-up fixes for Redis and Postgres. It opens with what to check before upgrading. Co-Authored-By: Claude <noreply@anthropic.com>
Pushing a tag vX.Y.Z now publishes both packages. Earlier npm versions were
published by hand, and the Python package has never been published.
build tag names the version in all five files, tagged commit is on
main, pnpm build, npm pack, uv build
verify no checkout: the tarball, sdist and wheel hold only the
package, twine check passes, each installs alone and imports
publish-npm npm publish of the verified tarball, environment `npm`
publish-pypi pypa/gh-action-pypi-publish on the verified files,
environment `pypi`
Both registries use trusted publishing, so no token is stored. Only the two
publish jobs can ask for an OIDC token, and neither runs anything from the
repo: they download what verify checked and upload it. npm attaches
provenance and the PyPI action uploads attestations without extra flags.
A pull request runs build and verify, so a packaging break shows up before a
tag exists. The publish jobs run only for a tag push.
Actions are pinned by major version, as in the other workflows.
Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sets the version to 0.3.0, adds a changelog, and adds the workflow that publishes both packages when a version tag is pushed. Merging this publishes nothing.
verifychecked and upload them.scripts/check-version.mjsreadspackage.json,python/pyproject.toml,python/uv.lock,.claude-plugin/plugin.jsonandsrc/internal/version.ts. It fails when they disagree, or when a tag names another version.pnpm checkruns it. The version the MCP server reports was a literal'0.2.0'in two places insrc/server/http.ts; it is now that one constant.CHANGELOG.mdis new. The 0.3.0 entry covers feat(notice): fold repeats and the steps of one act into one line #41 to Separate counted settlement from background retention #48, the Python package (feat(python): a Python port of attend, with one conformance suite for both #39, refactor(python): publish as aqi-attend, imported as aqi_attend #40), and the twoattend servefixes fix(serve): wait on the Redis decision log with a blocking connection #36 and fix(serve): wake Postgres subscribers through LISTEN, not the next poll #38. Those two merged two days after 0.2.0 reached npm, and the 0.2.0 tarball does not have them. The entry opens with what to check before upgrading.aqi-attend. The sdist holds the package, README, license andpyproject.tomland nothing else. The Python README's links are absolute, because PyPI renders it on its own page.The workflow follows the registries' documentation as it reads on 2026-11-14:
ubuntu-latest(it ships npm 11.19.1), and a step that refuses an older npmid-token: write; provenance is added without a flag for a public package from a public repopublish-npmonly; no--provenancerepository.urlinpackage.jsonmust match the repopypa/gh-action-pypi-publish,id-token: writeon the job, in an environmentpublish-pypi, environmentpypibuildandverifyhold no OIDC permissionrelease.ymlitselfActions are pinned by major version, as in
ci.yml.Before the first tag
These two forms can only be filled in by an owner of each registry account. npm treats every field as case-sensitive.
npmjs.com, package
@acquiredintelligence/attend, Settings, Trusted publishing, GitHub Actions:acquiredintelligenceattendrelease.ymlnpmnpm publish. A publisher created today allows onlynpm stage publishuntil this is ticked.pypi.org, account sidebar, Publishing, "Add a new pending publisher", GitHub:
aqi-attendacquiredintelligenceattendrelease.ymlpypinpm drops a trusted publisher that has not published within 2 days of being created, so add it shortly before tagging. PyPI's pending publisher does not reserve the name
aqi-attend; it is free today.Then merge, and tag the merge commit on main:
git tag -a v0.3.0 -m "attend v0.3.0" && git push origin v0.3.0.Evidence
aqi-attendhas never been published. The sdist built from main holds 74 entries, with 26 test files, the bench anduv.lock. The Python README's 12 links to the docs are relative.After: the same sdist holds 46 entries, all of them the package, README, license,
PKG-INFO,pyproject.tomland.gitignore.Run locally on the head of this branch, Node 26.10 and npm 11.19.1, Redis 7 and Postgres 17 in Docker:
Every
runstep ofbuildandverifywas also extracted fromrelease.ymland run locally withbash -eo pipefail, once with no tag and once as tagv0.3.0: all exit 0. On this branch the "tagged commit is on main" step refuses, as it should. The tarball installed into an empty project adds 1 package; the wheel installed into an empty Python 3.12 environment adds 1 package. Each README's first sample, run against those installs, prints:The built server answers
initializewith"serverInfo":{"name":"attend","version":"0.3.0"}.Not proven: the two publish jobs have never run. They need the registry setup above and a real tag.
Merge Danger
Door: two-way for the merge, one-way at the tag.
Merging changes version strings, docs and CI. Pushing
v0.3.0afterwards publishes 0.3.0 to both registries, and neither lets a version be replaced once it is up.Blast Radius: release
Every pull request gains two short checks,
buildandverify. If one registry's publish fails, the other still goes out; fix the setup and re-run the failed job. The publish jobs create the environmentsnpmandpypion first use, with no protection rules.🤖 Generated with Claude Code