chore: switch to published @percy/maestro-web@0.1.0-alpha.0#2
Draft
AkashBrowserStack wants to merge 1 commit into
Draft
chore: switch to published @percy/maestro-web@0.1.0-alpha.0#2AkashBrowserStack wants to merge 1 commit into
AkashBrowserStack wants to merge 1 commit into
Conversation
Replace the local file: dependency with the exact alpha version published to npm. Exact pin (no caret) because caret semantics on pre-release versions are not what most users expect — bump explicitly per alpha. yarn.lock will be regenerated once the SDK is published to npm.
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.
Summary
Replaces the local `file:../percy-maestro-web` dev-dependency with the alpha version that will be published to npm: `@percy/maestro-web@0.1.0-alpha.0`.
Pinned exactly (no caret) because caret semantics on pre-release versions don't behave as expected — `^0.1.0-alpha.0` only matches `0.1.0-alpha.X`, never advances to `0.1.0`. Better to bump explicitly per alpha.
Marked as draft — depends on the SDK actually being published. Sequence:
Why
Tracked under PER-7788. The example currently consumes the SDK via a relative path, which only works when both repos are checked out side-by-side. After the alpha publish, end users following the example should be able to `yarn install` straight from the registry.
Test plan
🤖 Generated with Claude Code