fix(tin-2435): bump tummycrypt_tinyland_auth to 0.4.0 (A4 propagation)#13
Merged
Merged
Conversation
Consumer-bump for TIN-2435 (A4 propagation). Bumps the tummycrypt_tinyland_auth bazel_dep pin from 0.3.0 to 0.4.0 to pick up the P2 view-grants RBAC data reconciliation (moderator/editor/contributor gain admin.events.view; event_manager gains admin.content.view) plus new ROLE_CHARTER, MEMBER_SELF_SERVICE_CORE, and FEATURE_DOMAINS exports. This repo (tinyland-security) does not itself reference the auth package's role/permission matrix in src or tests (grep-verified), so no test assertions needed updating. package.json/pnpm-lock.yaml are left untouched: the auth dep there is a caret range (^0.3.0 / peer ^0.2.2 || ^0.3.0), not an exact pin, and there is no CI parity check tying the npm range to the Bazel pin, so per house rule the Bazel module graph remains the sole source of truth for this bump. No MODULE.bazel.lock exists in this repo, so no lockfile regeneration was required. Verified locally: pnpm typecheck, pnpm test (119/119 passing), pnpm build, pnpm check:package, and bazelisk build/test //:pkg //:test all green with the new pin resolved from the tinyland-inc bazel-registry.
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
Consumer-bump for TIN-2435 (A4 propagation).
tummycrypt_tinyland_auth0.4.0was just promoted in
tinyland-inc/bazel-registry; this repo was still pinnedto 0.3.0 in
MODULE.bazel.bazel_dep(name = "tummycrypt_tinyland_auth", ...)from0.3.0→0.4.0.moderator/editor/contributor gain
admin.events.view;event_managergainsadmin.content.view; new exportsROLE_CHARTER,MEMBER_SELF_SERVICE_CORE,FEATURE_DOMAINS.src/andtests/do not reference the authpackage's role/permission matrix at all, so no test assertions required
changes.
package.json/pnpm-lock.yamlleft untouched: the auth dependency thereis a caret range (
^0.3.0dev,^0.2.2 || ^0.3.0peer), not an exact pin,and there's no CI step tying the npm range to the Bazel pin. Per house
convention, the Bazel module graph is the source of truth for in-ecosystem
deps, not npm resolution.
MODULE.bazel.lockexists in this repo, so no lockfile regenerationwas needed.
Test plan
pnpm typecheck— cleanpnpm test— 119/119 passing (identical to pre-bump baseline)pnpm build— cleanpnpm check:package(publint) — all goodbazelisk build //:pkg //:test— green, resolves 0.4.0 fromtinyland-inc/bazel-registry(local disk-cache only, no RBE touched —this repo's
.bazelrchas no remote-execution config)bazelisk test //:test— 1/1 passing