ci/circleci: RELEASE_CHANNEL_stable_yarn_build
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_build
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_build_prod
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_dom_fixtures
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_persistent
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_prod
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_prod_www
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_prod_www_variant
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_www
Your tests passed on CircleCI!
Details
ci/circleci: RELEASE_CHANNEL_stable_yarn_test_www_variant
Your tests passed on CircleCI!
Details
ci/circleci: build_devtools_and_process_artifacts
Your tests passed on CircleCI!
Details
ci/circleci: process_artifacts
Your tests passed on CircleCI!
Details
ci/circleci: process_artifacts_experimental
Your tests passed on CircleCI!
Details
ci/circleci: setup
Your tests passed on CircleCI!
Details
ci/circleci: sizebot_experimental
Your tests passed on CircleCI!
Details
ci/circleci: sizebot_stable
Your tests passed on CircleCI!
Details
ci/circleci: yarn_build
Your tests passed on CircleCI!
Details
ci/circleci: yarn_flow
Your tests passed on CircleCI!
Details
ci/circleci: yarn_lint
Your tests passed on CircleCI!
Details
ci/circleci: yarn_lint_build
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_build
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_build_devtools
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_build_prod
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_prod
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_prod_www
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_prod_www_variant
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_www
Your tests passed on CircleCI!
Details
ci/circleci: yarn_test_www_variant
Your tests passed on CircleCI!
Details
ci/codesandbox
Building packages succeeded.
Details
In order to help an internal issue with leaking memory from fibers, we should clear the
siblingfield when we mark a fiber for deletion. We previously did this in #16820 but this caused internal errors because there are subtle use cases with the deprecatedfindDOMNodewhen we need thesiblingfor traversal.Instead of clearing the
siblingfield at this point, we could also maybe clear it when we also clear thenextEffect. This should happen at a later time, after thefindDOMNodelogic has run, allowing the field to properly be cleared and the retained fiber to be GC'd.