fix(tin-2435): bump tummycrypt_tinyland_auth to 0.4.0 (A4 propagation) - #10
Merged
Merged
Conversation
Consumes the P2 view-grant reconciliation from tinyland-auth 0.4.0 (TIN-2435, operator-ratified 2026-07-04; precedent TIN-1606): moderator, editor, and contributor gain admin.events.view; event_manager gains admin.content.view; every role at or above member now holds the member self-service core. This package only imports the type-only `AdminRole` from @tummycrypt/tinyland-auth (src/schemas.ts) and defines its own local ADMIN_ROLES / ADMIN_PERMISSIONS validation constants, independent of tinyland-auth's ROLE_PERMISSIONS matrix. No test assertions reference the upstream permission grants, so no test changes were required. Verified: all 138 tests pass unchanged both before (0.2.2) and after (0.4.0) the bump via `bazelisk test //:test`. No MODULE.bazel.lock present in this repo (nothing to regenerate). package.json/pnpm-lock.yaml carry no npm dependency on @tummycrypt/tinyland-auth or @tinyland-inc/tinyland-auth (npm resolution was retired for this dep in #9); left untouched per house rule that in-ecosystem deps resolve via the Bazel module graph.
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.
Summary
tummycrypt_tinyland_authbazel_depinMODULE.bazelfrom0.2.2to0.4.0(TIN-2435, A4 propagation; tinyland-auth 0.4.0 promoted inbazel-registry).admin.events.view;event_managergainsadmin.content.view; every role at/above member gets the member self-service core), new exportsROLE_CHARTER,MEMBER_SELF_SERVICE_CORE,FEATURE_DOMAINS.AdminRoleexport from@tummycrypt/tinyland-auth(src/schemas.ts) and defines its own localADMIN_ROLES/ADMIN_PERMISSIONSconstants independent of tinyland-auth'sROLE_PERMISSIONSmatrix — none of the new grants are exercised by this repo's assertions, so no test changes were needed.Changes
MODULE.bazel:tummycrypt_tinyland_auth0.2.2→0.4.0.MODULE.bazel.lockexists in this repo — nothing to regenerate.package.json/pnpm-lock.yamluntouched: no npm dependency on@tummycrypt/tinyland-author@tinyland-inc/tinyland-authexists (npm resolution for this dep was retired in feat(bazel): resolve tinyland-auth via module graph (retire npm) #9); in-ecosystem deps resolve via the Bazel module graph per house convention.Test plan
bazelisk build //:pkg //:test— succeeds, resolvestummycrypt_tinyland_auth0.4.0 fromtinyland-inc/bazel-registry.bazelisk test //:test— 138/138 tests pass (same count/pass as pre-bump baseline on 0.2.2).//:pkg //:testviajs-bazel-package.yml) to confirm in-CI resolution.