Repository navigation
Add key-only direct QA uploads to the capture package - #66
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.
Applications can now initialize
@replayio/self-healing-capturewith onlyinitCapture({ publishableKey })and upload directly to Replay QA. The package uses the fixed internalreplayrecorder alias and authenticates the existing recorder request/beacon hooks; QA owns the actual organization and regional routing. It sends session identifiers and existing auxiliary artifacts without an application-owned forwarding route or remote QA wrapper import.Existing orgId/same-origin forwarding integrations remain supported. Includes the 0.1.8 version bump, npm dependency metadata, migration guidance, and managed-setup paths in the installation/update skills. The upstream
@fullstory/browserSDK uses its default FullStory CDN recorder delivery; no QA-hosted executable wrapper or recorder is loaded by new installations. This follows the SDK's standard npm integration model rather than bundling/forking the FullStory recorder.Validation: 20 targeted non-browser tests passed (capture startup, rollover, in-flight requests, retries, redaction, batching, direct authentication and transport boundaries), and
npm run build:capturepassed. The capture-browser test file uses VM mocks, not browser automation. CI will run the repository checks and existing browser suite. No deployed session verification or npm publication has been performed.Release coordination: publish 0.1.8 before deploying QA's new setup instructions. Direct mode requires the companion QA key-only capture/registration changes; legacy installations are unchanged.
Companion QA PR: https://github.com/replayio/loop-qa/pull/7055