chore: ship v0.23 (publish order, compatibility matrix, release notes, announcement)

Open
#561 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
cli, typescript
Domain
devops

Research direction

This is a release checklist rather than a code change: it asks to confirm v0.23 sub-issues, publish packages in order, update the compatibility matrix and adapter manifest, write release notes, and announce. The payload names no files or tests to start from. Work on it requires maintainer access to publishing and the docs site, so it is not a starting point for a newcomer.

Written by the indexing model from the issue text.

Description

easy P2 v0.23

Why

A release is done when its work is shipped, documented, covered by a guide, and announced. This tracks the part that is not a feature.

What

  • Confirm every v0.23 sub-issue is closed or moved with a reason
  • Publish in order: @seamless-auth/types, API, OIDC provider edge, adapters, SDKs, console, CLI
  • Update the compatibility matrix and the adapter manifest
  • Release notes with the breaking changes and upgrade steps
  • Announce on the docs site and seamlessauth.com

Done when

v0.23 is installable from the quickstart and the announcement is live.

Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
11h 40m
Merged PRs (30d)
104

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fells-code/seamless-auth-api

All issues in fells-code/seamless-auth-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.