fix(deps): raise auth-public-client floor to ^0.5.1#383
Merged
Conversation
Bump the @tailor-platform/auth-public-client dependency floor from ^0.5.0 to ^0.5.1 so fresh installs can no longer resolve the broken 0.5.0 release. Exempt @tailor-platform/auth-public-client from the minimumReleaseAge maturity gate so 0.5.1 can be installed before it clears the 3-day window; the gate guards against compromised third-party republishes, not first-party Tailor packages. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
What
Bumps the
@tailor-platform/auth-public-clientdependency floor in@tailor-platform/app-shellfrom^0.5.0to^0.5.1, so fresh installs can no longer resolve the broken0.5.0release.Why
0.5.0is broken.^0.5.0resolves to>=0.5.0 <0.6.0, so a clean install could pick it up;^0.5.1narrows that to>=0.5.1 <0.6.0.Note: this only affects fresh installs. Consumers with an existing lockfile pinning
0.5.0will keep it until they update their lockfile — the old range still satisfies0.5.0.minimumReleaseAge exemption
0.5.1was published on 2026-07-14, which is inside this repo's 3-dayminimumReleaseAgewindow, sopnpm installrefused it. This PR adds@tailor-platform/auth-public-clientto a newminimumReleaseAgeExcludelist inpnpm-workspace.yaml, mirroring the existingtrustPolicyExcludepattern. The maturity gate exists to guard against compromised third-party republishes, not first-party Tailor packages.Caveat:
minimumReleaseAgeExcludematches on package name (glob), so this exempts all versions of the package, not just0.5.1.Changes
packages/core/package.json— floor bumppnpm-workspace.yaml—minimumReleaseAgeExcludefor the first-party packagepnpm-lock.yaml— resolves to0.5.1.changeset/— patch changeset🤖 Generated with Claude Code