Release
Changesets and npm release workflow
How hostfunc versions and publishes public packages, and the safeguards we run before any release.
Effective date: April 2026
What hostfunc publishes
Public npm publishing is currently scoped to:
@hostfunc/cli@hostfunc/sdk
Internal libraries (database/executor/tooling packages) are infrastructure dependencies and are not published as public package artifacts.
Release flow
- Create one or more changesets describing version intent.
- Changesets generates a version PR with package/changelog updates.
- After merge, release workflow runs validation gates and publishes eligible packages.
- Release provenance and npm metadata are emitted by the publish step when configured.
Release safeguards
- Monorepo install with frozen lockfile in CI.
- Lint, typecheck, and tests before release actions.
- CLI pack smoke test to validate installability and baseline command behavior.
- GitHub auth for release PR automation via
CHANGESETS_GITHUB_TOKEN.
Troubleshooting
- npm 404 on publish: package ownership/scope or publish target mismatch.
- No changesets found: release can still attempt publishing unpublished public packages.
- Frozen lockfile errors: run lockfile update after dependency/specifier changes before merging.