KEMBAR78
Comparing 93d7aa69...8a8e9a7e · facebook/react · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: facebook/react
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 93d7aa69
Choose a base ref
...
head repository: facebook/react
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 8a8e9a7e
Choose a head ref
  • 2 commits
  • 30 files changed
  • 2 contributors

Commits on Sep 12, 2025

  1. Release Activity in Canary (#34374)

    ## Overview
    
    This PR ships `<Activity />` to the `react@canary` release channel for
    final feedback and prepare for semver stable release.
    
    ## What this means
    
    Shipping `<Activity />` to canary means it has gone through extensive
    testing in production, we are confident in the stability of the feature,
    and we are preparing to release it in a future semver stable version.
    
    Libraries and frameworks following the [Canary
    Workflow](https://react.dev/blog/2023/05/03/react-canaries) should begin
    implementing and testing the feature.
    
    ## Why we follow the Canary Workflow
    
    To prepare for semver stable, libraries should test canary features like
    `<Activity>` with `react@canary` to confirm compatibility and prepare
    for the next semver release in a myriad of environments and
    configurations used throughout the React ecosystem. This provides
    libraries with ample time to catch any issues we missed before slamming
    them with problems in the wider semver release.
    
    Since these features have already gone through extensive production
    testing, and we are confident they are stable, frameworks following the
    [Canary Workflow](https://react.dev/blog/2023/05/03/react-canaries) can
    also begin adopting canary features like `<Activity />`.
    
    This adoption is similar to how different Browsers implement new
    proposed browser features before they are added to the standard. If a
    frameworks adopts a canary feature, they are committing to stability for
    their users by ensuring any API changes before a semver stable release
    are opaque and non-breaking to their users.
    
    Apps not using a framework are also free to adopt canary features like
    Activity as long as they follow the [Canary
    Workflow](https://react.dev/blog/2023/05/03/react-canaries), but we
    generally recommend waiting for a semver stable release unless you have
    the capacity to commit to following along with the canary changes and
    debugging library compatibility issues.
    
    Waiting for semver stable means you're able to benefit from libraries
    testing and confirming support, and use semver as signal for which
    version of a library you can use with support of the feature.
    
    ## Docs 
    
    Check out the ["React Labs: View Transitions, Activity, and
    more"](https://react.dev/blog/2025/04/23/react-labs-view-transitions-activity-and-more#activity)
    blog post, and [the new docs for
    `<Activity>`](https://react.dev/reference/react/Activity) for more info.
    
    ## TODO
    - [x] Bump Activity docs to Canary
    reactjs/react.dev#7974
    
    ---------
    
    Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
    rickhanlonii and eps1lon authored Sep 12, 2025
    Configuration menu
    Copy the full SHA
    68f00c9 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8a8e9a7 View commit details
    Browse the repository at this point in the history
Loading