Repository navigation
chore: synchronize published CLI v0.53.0 - #35
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.
Align the installed CLI, source tag, engine lock and browser metadata with published v0.53.0 (source
476209d681a3482a864db6534f4eda4150aa59b0). Preserve the corpus and detector bytes.Validation: Astra cleared exact head
dca1acf05d4c5f026249345eb892ac745c99d6af; engine build/corpus sync/check and 63 tests pass. All 136 installed package files match the authenticated npm archive. Actual local browser clicks match the published CLI on all 57 corpus cases. Public Pages verification follows merge.