chore: adopt changesets and bring release tooling to org baseline - #5
Merged
Conversation
Bccorb
added a commit
that referenced
this pull request
Jul 29, 2026
Bumps @seamless-auth/types a minor. The consolidation is additive, and the three changes to existing schemas widen what they accept rather than narrowing it, so nothing breaks at runtime. Each does change an inferred type, which the changeset spells out. The changeset tooling itself lands in #5; this file is inert until that merges.
Bring this repo in line with seamless-auth-react. Changesets: - add @changesets/cli, .changeset/config.json, and RELEASES.md - replace the tag-triggered publish workflow with the changesets release workflow, which opens a version PR, then publishes to npm, tags, and creates the GitHub Release when that PR merges - publish with provenance CI: - run the test suite, which the previous workflow never did, and collect coverage - verify package contents with npm pack --dry-run - pin the runner actions to v6, matching the other repos Packaging fixes found along the way: - build now clears dist first, so a build no longer carries artifacts from a previous branch into the tarball (79 files down to 31) - the exports map declares its types condition explicitly, so node16 and nodenext consumers resolve declarations through it - license uses the current AGPL-3.0-only SPDX identifier - lint-staged covers json, md, and yaml alongside ts
#4 merged before its changeset landed, so the consolidation would have shipped without a version bump or changelog entry. Carrying the changeset here, where the tooling that consumes it is introduced. Minor rather than major: the consolidation is additive, and the three changes to existing schemas widen what they accept rather than narrowing it, so nothing breaks at runtime. Each does change an inferred type, which the changeset spells out.
Bccorb
force-pushed
the
chore/release-tooling
branch
from
July 29, 2026 00:57
ca521df to
1ed40c9
Compare
Contributor
Author
|
Rebased onto #4 merged before its changeset landed, so as things stand the schema consolidation is on
So merging this opens a single release PR that bumps |
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
1 participant
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.
Brings this repo's tooling in line with
seamless-auth-react. It already had commitlint, husky, prettier, eslint, and a CI workflow, so this fills the gaps rather than starting over.Changesets
@changesets/cli,.changeset/config.json(copied from the react repo), andRELEASES.mdchangeset,version-packages, andrelease:stablescriptspublish.ymlis replaced byrelease.yml, which useschangesets/action. Merging a changeset tomainopens a version PR; merging that PR publishes to npm, creates the Git tag, and creates the GitHub Release.NPM_CONFIG_PROVENANCE=trueRELEASES.mdincludes a section on choosing the bump, since a schema change here ripples through every consumer and the default should be "breaking until argued otherwise".CI
npm pack --dry-runPackaging fixes found while wiring this up
builddid not cleandist/first. Switching branches and rebuilding left the previous branch's compiled output in place, andfiles: ["dist"]would have published it. The pack preview went from 79 files to 31 oncebuildwas changed tonpm run clean && tsc.exportswas{".": "./dist/index.js"}with notypescondition. Consumers onnode16ornodenextresolution were relying on the fallback. Now declared explicitly.licensewasAGPL-3.0, a deprecated SPDX identifier. NowAGPL-3.0-only, matching the other packages.CHANGELOG.mdadded tofilesso it ships with the package.lint-stagedonly covered*.ts; it now covers json, md, and yaml too.CHANGELOG.mdis in.prettierignore, so changesets' generated formatting cannot failformat:checkon a release PR.Before merging
NPM_TOKENneeds publish access on this repo for the release workflow.CODECOV_TOKENis referenced by the coverage upload step, which only runs on pushes tomain. If it is not configured the step is a no-op rather than a failure, but worth setting.Checks
npm run typecheck,npm run lint,npm run format:check,npm test,npm run build, andnpm run check-npm-buildall pass.npx changeset statusreports the patch bump.Note on ordering: #4 is open and will need a changeset added once this lands.