release(sdk): publish @beyond.dev/flags alongside @beyond.dev/kv at 0.2.0#10
Merged
Conversation
….2.0 The Release SDK workflow only published @beyond.dev/kv, so the flags adapter and OpenFeature providers added in #9 had no path to npm. Wire the workflow to publish both packages from the same sdk/v* tag (lockstep): - release-sdk.yml: set the tag version on both kv and flags (--allow-same-version), pin flags' @beyond.dev/kv dependency to ^<version>, build all workspaces, then publish kv first and flags second so the pinned dependency is resolvable the moment flags lands. - Bump @beyond.dev/kv and @beyond.dev/flags to 0.2.0 and replace the flags "@beyond.dev/kv": "*" dependency with "^0.2.0"; sync package-lock. Verified: both packages' export maps fully resolve to built files, npm pack --dry-run includes every dist target (kv: index/next/cache; flags: index/adapter/4 middleware/2 openfeature), full flags suite 153/153 green, all workspaces typecheck. Note: publishing @beyond.dev/flags via OIDC requires it to be registered as a trusted publisher on npm (same as @beyond.dev/kv). Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
The Release SDK workflow only published @beyond.dev/kv, so the flags adapter and OpenFeature providers added in #9 had no path to npm. Wire the workflow to publish both packages from the same sdk/v* tag (lockstep):
Verified: both packages' export maps fully resolve to built files, npm pack --dry-run includes every dist target (kv: index/next/cache; flags: index/adapter/4 middleware/2 openfeature), full flags suite 153/153 green, all workspaces typecheck.
Note: publishing @beyond.dev/flags via OIDC requires it to be registered as a trusted publisher on npm (same as @beyond.dev/kv).