chore: version packages#65
Merged
Merged
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@taskless/cli@0.10.2
Patch Changes
forward-compatible with the server's coming identity cleanup.
installationId. It is dropped from theWhoamiOrgtypeand from the
taskless rule meta --jsonoutput (it was already optional andabsent for public repos). The CLI never used it and it should not round-trip
through us.
WhoamiOrg.orgIdis now optional and a newgithubOrgId?: numberis added, so a consumer readsgithubOrgId ?? orgIdand keeps working across the server's rename. It is a convenience id, never an
identity.
decodeOrgIdvalidates the token'sidclaim (a UUID string) and the legacy
orgIdclaim (numeric, or a numericstring) independently: a valid
idwins, an invalididstill lets a validorgIdthrough, and a non-numericorgIdis rejected rather than smuggled inas an identity. PostHog then groups organizations on that canonical id. Tokens
that don't yet carry an
idclaim fall back to the numeric claim, so groupingis unchanged until the server starts sending it.
resolves, the canonical id falls back to the nil UUID
(
00000000-0000-0000-0000-000000000000) instead of being absent — so the orgsubject and telemetry group are always a stable, known value and unattributed
usage lands in one bucket. As a result, a write from a token missing org info
now sends the nil-UUID subject rather than failing with a re-authenticate
error.
number | stringon the legacy path. The canonicalidstays aUUID
string, butdecodeOrgIdaccepts either type since we can't promisewhat a legacy claim carries.