Conversation
Keep sourcemap fixtures within the release and upload flows supported by their local API mocks. Disable CLI telemetry for E2E builds while preserving the SDK telemetry under test. Co-Authored-By: GPT-6 (OpenAI) <codex@openai.com>
Contributor
size-limit report 📦
|
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.
Sourcemap fixtures inherit automatic release commit association, but their local API mocks do not implement repository discovery. Disable commit association in those fixtures so builds only exercise the release and sourcemap flows they assert.
Opt E2E builds out of CLI telemetry in both the local runner and CI. The CLI-specific setting preserves the SDK telemetry exercised by the tests.
Local config and environment checks pass. Framework E2E validation remains for CI; a local runner lint diagnostic also reproduces on the base revision.