Skip to content

docs: align kit release truth with 0.9.1 #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jesssullivan merged 1 commit into from
Jun 13, 2026
Merged

docs: align kit release truth with 0.9.1 #108

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Closed but still relevant context:
- `TIN-103` closed the release-authority ambiguity for `Jesssullivan/scheduling-kit`
- `TIN-104` was canceled as a duplicate during that convergence work
- `TIN-165` is done: the tinyland bazel-registry is generated from standalone
package truth and currently carries scheduling-kit `0.9.0+` and
package truth and currently carries scheduling-kit `0.9.1+` and
scheduling-bridge `0.5.11+`; the registry line is in `.bazelrc`
- `TIN-677` is done: HomegrownAdapter takes injected schemas from
`@tummycrypt/tinyland-business-pg`, with `tinyland-auth-pg` kept only as an
Expand All @@ -66,9 +66,9 @@ Current operational truth:

- local development should default to `jesssullivan/main`
- that branch is the current functional release line
- current released version is `0.9.0`: git tag plus GitHub Release, GitHub
- current released version is `0.9.1`: git tag plus GitHub Release, GitHub
Packages `@jesssullivan/scheduling-kit`, and the active tinyland Bazel
registry (`0.9.0+`)
registry (`0.9.1+`)
- npmjs `@tummycrypt/scheduling-kit` is retired for new versions and frozen at
`0.8.0`; `npm_publish_mode: disabled` is permanent policy, not a temporary
outage
Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ The Bazel module graph is the canonical delivery mechanism. Depend on the
module through the tinyland Bazel registry:

```starlark
bazel_dep(name = "tummycrypt_scheduling_kit", version = "0.9.0")
bazel_dep(name = "tummycrypt_scheduling_kit", version = "0.9.1")
```

with the registry line (already in this repo's `.bazelrc`):
Expand Down Expand Up @@ -105,7 +105,7 @@ Current reality:
- the functional release line is `Jesssullivan/scheduling-kit`
- `tinyland-inc/scheduling-kit` is now a downstream mirror and validation
surface, not a second publish authority
- the active tinyland Bazel registry carries `scheduling-kit` `0.9.0+` (and
- the active tinyland Bazel registry carries `scheduling-kit` `0.9.1+` (and
`scheduling-bridge` `0.5.11+`); the registry line is already in `.bazelrc`

Treat `Jesssullivan/main` as the release authority for package publication and
Expand Down
Loading