Release checklist

A repeatable checklist for shipping a coordinated ifURI release across the runtime, connector packages, examples and app docs. The goal is that every public install snippet, manifest and catalog entry points at the same tested versions.

1. Runtime (urirun)

• [ ] Tests green on the target commit (make test in if-uri/urirun).
• [ ] Versions bumped in one move: make release-bump V=<x.y.z> (then make version-check is green across all five version files).
• [ ] CHANGELOG frozen: fold the ## [Unreleased] section into ## [<x.y.z>] and dedupe any auto-fix-daemon entries (the linter appends mislabelled ## [0.1.10] ticket blocks — collapse them) so the release section is the single source of truth.
• [ ] Tag and push: make release (tags v<x.y.z> from adapters/python/VERSION, pushes; CI release.yml builds + publishes to PyPI).
• [ ] Move install pins to the new tag in one move (only *after* the tag exists): bash if-uri/ifuri-com/scripts/apply-release-pins.sh v<x.y.z> — sweeps docs, the website, get-urirun-com node/host, app and connector pyproject pins.

2. Connector packages

For each urirun-connector-* package:

• [ ] Package version bumped; connector.manifest.json and urirun_bindings() describe the same routes.
• [ ] make docker-test passes (CLI, registry compile, urirun run, MCP tools, A2A card).
• [ ] README links back to the connect.ifuri.com hub page and docs.ifuri.com.
• [ ] Hub catalog entry (connect.ifuri.com/data/connectors/<id>/manifest.json) updated and validated: curl -fsS https://connect.ifuri.com/validate-connector --data @manifest.json.

3. Connector hub (connect.ifuri.com)

• [ ] python3 tools/build_catalog.py regenerates connectors.json, registry.json, search.json, llms.txt and sitemap.xml.
• [ ] bash tests/smoke.sh passes.
• [ ] docs.ifuri.com/connectors.html status list matches the catalog (available vs planned).

4. Examples

• [ ] Numbered examples build and pass (make test, plus make test-full for 11-novnc_lan_flow).
• [ ] Heavy Docker examples pin image tags for reproducible CI.
• [ ] Example install/run commands reference the released runtime tag.

5. App and host docs

• [ ] if-uri/app README, CHANGELOG, VERSION and the urirun @ …@<tag> pin in pyproject.toml reflect the release.
• [ ] get.urirun.com default URIRUN_REF (in node.sh and host.sh) points at the released tag — this is the installer users actually run. get.ifuri.com hosts the app download and 301-redirects /node.sh to get.urirun.com.
• [ ] ifuri.com download copy aligned: app version is live from GitHub Releases; the urirun runtime tag is current.
• [ ] Apply pins in one move with bash if-uri/ifuri-com/scripts/apply-release-pins.sh <tag> (only after the tag is pushed), then redeploy get.urirun.com + docs.

6. Cross-repository sync

• [ ] Work summary in if-uri/docs updated for the release.
• [ ] Roadmap entries reflect shipped vs planned work.
• [ ] All TODO.md / CHANGELOG.md files touched by the release updated.

Related

• Connectors - catalog, package shape and trust model.
• Connector authoring - build a connector package.
• Getting started - install and run a URI.