Merge branch 'main' into chore/release_14_3_0

Author: jennifer-shehane

CONTRIBUTING.md

@@ -102,9 +102,9 @@ You can learn about how to import markdown & partials
 ### Adding Plugins
 
 To add a plugin, submit a [pull request](#Pull-Requests) with the corresponding
-data added to the [`plugins.json`](/src/data/plugins.json) file. Your plugin
-should have a name, description, link to the plugin's code, as well as any
-keywords.
+data added to the [`plugins.json`](/src/data/plugins.json) file.
+Your plugin entry should have a name, description, link to the plugin's code (for example to a repository on GitHub),
+as well as any keywords.
 
 We want to showcase plugins that work and have a good developer experience. This
 means that a good plugin generally has:
@@ -122,8 +122,13 @@ Each plugin submitted to the plugins list should have the following:
    - Demonstrates the plugin working
    - Acts as real-world example usage
 
-2. CI pipeline
-3. Compatibility with at least the latest major version of Cypress
+1. CI pipeline
+1. Compatibility with at least the latest major version of Cypress
+1. Populated [package-json](https://docs.npmjs.com/cli/v11/configuring-npm/package-json) fields
+
+   - [homepage](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#homepage)
+   - [repository](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#repository) for the command [npm repo](https://docs.npmjs.com/cli/v11/commands/npm-repo)
+   - [bugs](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#bugs) for the command [npm bugs](https://docs.npmjs.com/cli/v11/commands/npm-bugs)
 
 Plugins are listed in the following order:
 

docs/accessibility/changelog.mdx

@@ -9,6 +9,10 @@ sidebar_position: 200
 
 # Changelog
 
+## Week of 3/24/2025
+
+- Cypress Accessibility results are now included in the [Data Extract API](/cloud/integrations/data-extract-api) so that you can retrieve data over time.
+
 ## Week of 3/10/2025
 
 - The [Cypress Accessibility Results API](/accessibility/results-api) has been updated with additional details about accessibility scores and failed element counts at the run level. Also, view-level reporting has been added, breaking out accessibility report data by the pages and components covered in the report. These improvements support more advanced workflows based on the accessibility data in the API, such as alerting a specific team about violations in a part of the app they own, or implementing different standards for different parts of the application.

docs/app/continuous-integration/overview.mdx

@@ -260,8 +260,11 @@ Cypress Docker images are available from:
 - [cypress/browsers](https://github.com/cypress-io/cypress-docker-images/tree/master/browsers) builds on the
   [cypress/base](https://github.com/cypress-io/cypress-docker-images/tree/master/base) image.
   For `Linux/amd64` images it adds **Chrome**, **Firefox** and **Edge** browsers.
+  For `Linux/arm64` images it adds only **Firefox** browsers from version `136.0.2` and above.
+  Chrome and Edge browsers are currently not available for `Linux/arm64`.
   A corresponding image `<tag>` allows selection of the combined Node.js and browser versions.
-  (Currently `Linux/arm64` images do **not** contain browsers.)
+  The version tags for the unavailable Chrome and Edge browsers on the `Linux/arm64` platform are empty place-holders only,
+  required for multi-platform support compatibility.
 
 - [cypress/included](https://github.com/cypress-io/cypress-docker-images/tree/master/included) builds on the
   [cypress/browsers](https://github.com/cypress-io/cypress-docker-images/tree/master/browsers) image.

docs/app/get-started/install-cypress.mdx

@@ -107,7 +107,7 @@ Cypress supports running under these operating systems:
 - **Linux** Ubuntu 20.04 and above, Fedora 40 and above, and Debian 11 and above _(x64 or arm64)_
   (see [Linux Prerequisites](#Linux-Prerequisites) down below)
 - **Windows** 10 and above _(x64)_
-- **Windows Server** 2019 and 2022 _(x64)_
+- **Windows Server** 2019, 2022 and 2025 _(x64)_
 
 ### Node.js
 
@@ -135,6 +135,10 @@ Attempting to use it as a non-root user may result in permissions errors.
 
 :::
 
+If you are using a [Cypress Docker image](../continuous-integration/overview#Cypress-Docker-variants),
+you will find a fixed version of Node.js is pre-installed in the image.
+You select the Node.js version using the Docker image tag.
+
 ### Package Manager
 
 Cypress is [installed](#Install) using one of the following supported package managers:
@@ -146,18 +150,17 @@ Cypress is [installed](#Install) using one of the following supported package ma
 | [Yarn (Modern aka berry)](https://yarnpkg.com/)  | `4.x` and above     | [Yarn Installation](https://yarnpkg.com/getting-started/install)                                                |
 | [pnpm](https://pnpm.io/)                         | `8.x` and above     | [pnpm Installation](https://pnpm.io/installation)                                                               |
 
-:::caution
-
-<strong>Yarn Configuration</strong>
+#### Yarn Configuration
 
-[Yarn (Modern)](https://yarnpkg.com/) configuration using [`nodeLinker: "node-modules"`](https://yarnpkg.com/configuration/yarnrc#nodeLinker)
-is preferred. Cypress [Component Testing](/app/core-concepts/testing-types#What-is-Component-Testing) is not currently compatible with the default setting [`nodeLinker: "pnp"`](https://yarnpkg.com/configuration/yarnrc#nodeLinker) which uses [Yarn Plug'n'Play](https://yarnpkg.com/features/pnp).
+[Yarn (Modern)](https://yarnpkg.com/) configuration using [nodeLinker: "node-modules"](https://yarnpkg.com/configuration/yarnrc#nodeLinker)
+is preferred. Cypress [Component Testing](/app/core-concepts/testing-types#What-is-Component-Testing) is not currently compatible with the default setting [nodeLinker: "pnp"](https://yarnpkg.com/configuration/yarnrc#nodeLinker) which uses [Yarn Plug'n'Play](https://yarnpkg.com/features/pnp).
 
-:::
+#### pnpm Configuration
 
-If you are using a [Cypress Docker image](../continuous-integration/overview#Cypress-Docker-variants),
-you will find a fixed version of Node.js is pre-installed in the image.
-You select the Node.js version using the Docker image tag.
+[[email protected]](https://github.com/pnpm/pnpm/releases/tag/v10.0.0) and above require allowlisting `cypress`.
+This enables Cypress to execute its `postinstall` script so it can install the Cypress binary into the [binary cache](/app/references/advanced-installation#Binary-cache).
+Refer to the [pnpm](https://pnpm.io/) configuration file documentation for additional information.
+[[email protected]](https://github.com/pnpm/pnpm/releases/tag/v10.4.0) introduced the CLI add option [--allow-build](https://pnpm.io/cli/add#--allow-build) to add the allowed build configuration directly through the command line.
 
 ### Hardware
 

docs/app/guides/cypress-studio.mdx

@@ -46,6 +46,7 @@ attribute to your Cypress configuration.
   yet work with Component Testing.
 - Cypress Studio does not support writing tests that use domains of [multiple
   origins](/app/guides/cross-origin-testing).
+- Cypress Studio can not interact with elements within a ShadowDom directly, though it can still run tests that do.
 
 ## Overview
 

docs/cloud/account-management/users.mdx

@@ -24,20 +24,24 @@ A user is anyone who logs in to Cypress Cloud.
 ## Invite users
 
 Organization [owner or admin](#User-roles) roles can invite
-[Cypress Cloud](https://on.cypress.io/cloud) users. Those invited will see all
-projects and tests run for the organization.
+[Cypress Cloud](https://on.cypress.io/cloud) users. Those invited will see
+the projects and tests the user has [team permissions](/cloud/account-management/teams#Assign-projects-to-a-team)
+to view.
 
 _Note: only owners can give other users 'owner' access._
 
 ### Invite a user to an organization:
 
 1. Select the [organization](/cloud/account-management/organizations) you
    want to invite a user to.
-2. Click **Users**, then **Invite User**.
-3. Fill in their email and select their [role](#User-roles), then click **Invite
-   User**.
-4. The user will receive an invitation email with a link to accept the
-   invitation.
+2. Click **Users & Teams**, then **Invite User**.
+3. Add one or more emails, pressing **Enter** after each one, and select their [role](#User-roles).
+4. Click **Invite User**.
+5. The user will receive an invitation email with a link to accept the invitation.
+
+If you prefer to send your own message to users and include a link to join the organization,
+you can click **Copy invite link** and all users who accept this invitation will be given
+the default role of **Member**.
 
 <DocsImage
   src="/img/cloud/users/invite-user-dialog.jpg"
@@ -82,51 +86,69 @@ See
 Users can be assigned roles that affect their access to certain features of
 [Cypress Cloud](https://on.cypress.io/cloud).
 
-- **Member:** Can see projects, runs, and keys.
-- **Admin:** Can also invite, edit and delete users.
-- **Owner:** Can also transfer or delete projects. Can delete and edit the
-  organization.
+- **Viewer:** Can see projects and runs but not make any changes.
+- **Member:** Can see projects, runs, record keys, and adjust App Quality configuration.
+- **Team Admin:** Can manage the member list for projects where the Team Admin is a member, and edit project configurations.
+- **Org Admin:** Can manage all users within the organization, and edit both organization and project configurations.
+- **Org Owner:** Can manage all aspects of the organization and projects.
 
 The permissions for each user role for Cypress Cloud:
 
-| Permission                                      | Member | Admin | Owner |
-| ----------------------------------------------- | ------ | ----- | ----- |
-| See test results of private projects            | ✅     | ✅    | ✅    |
-| See record keys of projects                     | ✅     | ✅    | ✅    |
-| See billing and usage information               |        | ✅    | ✅    |
-| Edit billing information                        |        | ✅    | ✅    |
-| See users invited to organization               |        | ✅    | ✅    |
-| Resend invitation to invited user               |        | ✅    | ✅    |
-| Invite 'member' to organization                 |        | ✅    | ✅    |
-| Invite 'admin' to organization                  |        | ✅    | ✅    |
-| See user requests to join organization          |        | ✅    | ✅    |
-| Accept user requests to join organization       |        | ✅    | ✅    |
-| Remove 'member' from organization               |        | ✅    | ✅    |
-| Remove 'admin' from organization                |        | ✅    | ✅    |
-| Edit 'member' in organization                   |        | ✅    | ✅    |
-| Edit 'admin' in organization                    |        | ✅    | ✅    |
-| Edit project name                               |        | ✅    | ✅    |
-| Edit project status (private/public)            |        | ✅    | ✅    |
-| Add or delete record keys                       |        | ✅    | ✅    |
-| Set up GitHub Integration                       |        | ✅    | ✅    |
-| Set up Slack Integration                        |        | ✅    | ✅    |
-| Invite 'owner' to organization                  |        |       | ✅    |
-| Edit 'owner' in organization                    |        |       | ✅    |
-| Remove 'owner' from organization                |        |       | ✅    |
-| Add, edit, remove user in personal organization |        |       | ✅    |
-| Edit organization name                          |        |       | ✅    |
-| Delete organization                             |        |       | ✅    |
-| Transfer project to another organization        |        |       | ✅    |
-| Delete project                                  |        |       | ✅    |
-| Set up SSO                                      |        |       | ✅    |
+**Organization-level permissions**
+
+| Permission                                | Viewer | Member | Team Admin | Org Admin | Org Owner |
+| ----------------------------------------- | ------ | ------ | ---------- | --------- | --------- |
+| See billing and usage information         |        |        |            | ✅        | ✅        |
+| Edit billing information                  |        |        |            | ✅        | ✅        |
+| Invite 'member' to organization           |        |        |            | ✅        | ✅        |
+| Invite 'admin' to organization            |        |        |            | ✅        | ✅        |
+| Invite 'owner' to organization            |        |        |            |           | ✅        |
+| See users invited to organization         |        |        |            | ✅        | ✅        |
+| Resend invitation to invited user         |        |        |            | ✅        | ✅        |
+| See user requests to join organization    |        |        |            | ✅        | ✅        |
+| Accept user requests to join organization |        |        |            | ✅        | ✅        |
+| Edit users in organization                |        |        |            | ✅        | ✅        |
+| Remove users from organization            |        |        |            | ✅        | ✅        |
+| Edit 'owner' in organization              |        |        |            |           | ✅        |
+| Remove 'owner' from organization          |        |        |            |           | ✅        |
+| Create and edit teams                     |        |        |            | ✅        | ✅        |
+| Assign projects to a team                 |        |        |            | ✅        | ✅        |
+| Remove projects from a team               |        |        |            | ✅        | ✅        |
+| Assign members to a team                  |        |        | ✅         | ✅        | ✅        |
+| Remove members from a team                |        |        | ✅         | ✅        | ✅        |
+| Set up organization GitHub Integration    |        |        |            | ✅        | ✅        |
+| Set up organization Slack Integration     |        |        |            | ✅        | ✅        |
+| Set up organization MS Teams Integration  |        |        |            | ✅        | ✅        |
+| Edit organization name                    |        |        |            |           | ✅        |
+| Delete organization                       |        |        |            |           | ✅        |
+| Set up SSO                                |        |        |            |           | ✅        |
+| View Enterprise Reporting                 | ✅     | ✅     | ✅         | ✅        | ✅        |
+
+**Project-level permissions**
+
+| Permission                               | Viewer | Member | Team Admin | Org Admin | Org Owner |
+| ---------------------------------------- | ------ | ------ | ---------- | --------- | --------- |
+| See test results of private projects     | ✅     | ✅     | ✅         | ✅        | ✅        |
+| See record keys of projects              |        | ✅     | ✅         | ✅        | ✅        |
+| Edit App Quality configuration           |        | ✅     | ✅         | ✅        | ✅        |
+| Edit project name                        |        |        | ✅         | ✅        | ✅        |
+| Edit project status (private/public)     |        |        | ✅         | ✅        | ✅        |
+| Add or delete record keys                |        |        | ✅         | ✅        | ✅        |
+| Configure project GitHub Integration     |        |        | ✅         | ✅        | ✅        |
+| Configure project Slack Integration      |        |        | ✅         | ✅        | ✅        |
+| Configure project MS Teams Integration   |        |        | ✅         | ✅        | ✅        |
+| Transfer project to another organization |        |        | ✅         | ✅        | ✅        |
+| Delete project                           |        |        | ✅         | ✅        | ✅        |
 
 ## User requests
 
-Users can "request" access to a given organization. If a developer on your team
-has access to Cypress and your project's source code - they can request to be
-given access to your organization. This means instead of you having to invite
-team members up front, they can request access and you can choose to accept or
-deny them access.
+Cypress App users can "request" access to a given organization. If a developer on
+your team has access to Cypress and your project's source code - they can request
+to be given access to your organization from within the Cypres App. This means
+instead of you having to invite team members up front, they can request access and
+you can choose to accept or deny them access.
+
+_Note: this option is not available if your Cloud organization is configured for SSO._
 
 <DocsImage
   src="/img/cloud/users/request-access-to-organization.png"