chore(web-sdk): bump @openpanel/web 1.1.0-local → 1.2.0-local - #316
Merged
Conversation
Minor bump to reflect the new client-side session_id generation feature added in this PR. Behavior change is additive (new code path with localStorage/sessionStorage UUIDs) with a backward-compat fallback to the legacy server-derived id, so no break for existing consumers — but worth distinguishing from 1.1.x for downstream publish + frameo-pro pinning.
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.
What
Bumps `@openpanel/web` from `1.1.0-local` to `1.2.0-local` so the next publish to GitHub Packages (`@dashverse/openpanel-web`) picks up the client-side session_id fix shipped in PR #315.
Why this is its own PR
The version bump was pushed AFTER PR #315 was already merged, so it sits separately on `feat/replay-client-session-id`. This is a clean cherry-pick onto a fresh branch from `main` so the diff is just the version field.
After merge
Publish `@dashverse/openpanel-web@1.2.0` to GitHub Packages via the existing publish flow.
Then frameo-pro bumps:
```json
"@dashverse/openpanel-web": "^1.2.0"
```
Related