Skip to content

release: v0.3.0, published to npm and PyPI from a tag - #49

Merged
asher-aqi merged 3 commits into
mainfrom
release/0.3.0
Nov 14, 2026
Merged

asher-aqi merged 3 commits into
mainfrom
release/0.3.0

Conversation

@asher-aqi

@asher-aqi asher-aqi commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

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.

push tag v0.3.0
  build         the tag names the version in all five files, and the tagged commit is on main
                pnpm build, npm pack, uv build
  verify        no checkout of the repo
                tarball, sdist and wheel hold only the package; twine check --strict
                each installs into an empty project and imports
  publish-npm   environment npm     npm publish of the verified tarball    OIDC, provenance
  publish-pypi  environment pypi    pypa/gh-action-pypi-publish            OIDC, attestations

pull request
  build, verify                     the two publish jobs are skipped

The workflow follows the registries' documentation as it reads on 2026-11-14:

The docs say Here
npm: npm 11.5.1 or later, Node 22.14 or later, GitHub-hosted runner Node 24 on ubuntu-latest (it ships npm 11.19.1), and a step that refuses an older npm
npm: id-token: write; provenance is added without a flag for a public package from a public repo set on publish-npm only; no --provenance
npm: repository.url in package.json must match the repo it does
npm: never use a dependency cache in a release build no cache in this workflow
PyPI: publish with pypa/gh-action-pypi-publish, id-token: write on the job, in an environment publish-pypi, environment pypi
PyPI: build in a separate job from the one that publishes build and verify hold no OIDC permission
PyPI: a reusable workflow cannot be the trusted publisher the publish jobs sit in release.yml itself

Actions 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:

  • Organization or user: acquiredintelligence
  • Repository: attend
  • Workflow filename: release.yml
  • Environment name: npm
  • Allowed actions: also allow npm publish. A publisher created today allows only npm stage publish until this is ticked.

pypi.org, account sidebar, Publishing, "Add a new pending publisher", GitHub:

  • PyPI Project Name: aqi-attend
  • Owner: acquiredintelligence
  • Repository name: attend
  • Workflow name: release.yml
  • Environment name: pypi

npm 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

  • Before: no release workflow; npm versions were published by hand and aqi-attend has never been published. The sdist built from main holds 74 entries, with 26 test files, the bench and uv.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.toml and .gitignore.

Run locally on the head of this branch, Node 26.10 and npm 11.19.1, Redis 7 and Postgres 17 in Docker:

pnpm check                47 files, 1656 passed, 2 skipped; check-snippets 43 blocks, all good;
                          check-version: 0.3.0 in 5 files
pnpm test:oracle          128 passed
pnpm bench:selfcheck      77 passed
uv run ruff check         All checks passed!        ruff format --check: 64 files already formatted
uv run pyright            0 errors, 0 warnings
uv run pytest             498 passed (Redis, Postgres and interop on)

npm pack --dry-run        270 files, 277.8 kB packed, 1.3 MB unpacked
                          dist/ 260, skills/ 7, README.md, LICENSE, package.json; nothing else
uv build                  aqi_attend-0.3.0.tar.gz (46 entries), aqi_attend-0.3.0-py3-none-any.whl (45)
twine check --strict      PASSED for both, with twine 7.0.0 on packaging 26.3 and on packaging 26.2,
                          the versions the PyPI action pins

Every run step of build and verify was also extracted from release.yml and run locally with bash -eo pipefail, once with no tag and once as tag v0.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:

[interrupt]
Build 4521 failed: 1 test
can you look?
Attend to this now, even mid-task.

The built server answers initialize with "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.0 afterwards 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, build and verify. 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 environments npm and pypi on first use, with no protection rules.

🤖 Generated with Claude Code


Devin Review

asher-aqi and others added 3 commits November 13, 2026 23:02
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>

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@asher-aqi
asher-aqi merged commit 20f749a into main Nov 14, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant