Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

• feat(transformer): class properties transform #7011
• test(transformer): script to amend Babel fixtures #7122
• feat(traverse): add methods to BoundIdentifier + MaybeBoundIdentifier to create SimpleAssignmentTargets #7418
• docs(traverse): fix docs for BoundIdentifier + MaybeBoundIdentifier #7417 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Docs only change, so merging without review.

Merge activity

• Nov 22, 5:58 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Nov 22, 5:58 AM EST: A user added this pull request to the Graphite merge queue.
• Nov 22, 6:04 AM EST: A user merged this pull request with the Graphite merge queue.

CodSpeed Performance Report

Merging #7417 will not alter performance

_{Comparing 11-22-docs_traverse_fix_docs_for_boundidentifier_maybeboundidentifier_ (be5f843) with main (27b2268)}

Summary

✅ 30 untouched benchmarks