Skip to content

docs: state that only express is linked with core for releases - #200

Merged
Bccorb merged 1 commit into
mainfrom
docs/linked-packages-policy
Oct 7, 2026
Merged

Bccorb merged 1 commit into
mainfrom
docs/linked-packages-policy

Conversation

@Bccorb

@Bccorb Bccorb commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Summary

README.md and RELEASES.md said "The core and official JavaScript adapters are linked". .changeset/config.json links only ["@seamless-auth/core", "@seamless-auth/express"], and the versions show it: core and express are 0.19.1, fastify 0.10.1, nextjs 0.3.1.

  • README.md and RELEASES.md "Pre-1.0 Policy": core and express are linked as a known-good set, and fastify and nextjs version independently.
  • RELEASES.md bullets: reworded to match.

The changeset config is unchanged. Whether to link fastify and nextjs too is a release-policy decision for maintainers.

Docs only, no changeset.

Testing

pnpm install --frozen-lockfile, pnpm check:types-current, and pnpm test pass (core 342, express 203, nextjs 155, fastify 146).

Closes #195

README.md and RELEASES.md said the core and official JavaScript adapters are linked in .changeset/config.json. The config links only @seamless-auth/core and @seamless-auth/express; @seamless-auth/fastify and @seamless-auth/nextjs release on their own versions.

Reword both files to describe the actual policy, and adjust the RELEASES.md pre-1.0 and after-v1 bullets so they refer to express rather than all adapters. The changeset config is unchanged; whether to link the other adapters is a separate release-policy decision.

Closes #195
@Bccorb
Bccorb merged commit 2351cde into main Oct 7, 2026
4 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.

docs: README and RELEASES say all adapters are linked, but only express is

1 participant