feat!: read code coverage config from Cypress.expose instead of Cypress.env#972
Merged
cacieprins merged 25 commits intomasterfrom Feb 10, 2026
Merged
feat!: read code coverage config from Cypress.expose instead of Cypress.env#972cacieprins merged 25 commits intomasterfrom
cacieprins merged 25 commits intomasterfrom
Conversation
mschile
reviewed
Jan 30, 2026
mschile
reviewed
Jan 30, 2026
Contributor
|
Searching for 'env' shows other mentions of 'env' that we probably want to update as well. |
mschile
requested changes
Jan 30, 2026
Contributor
mschile
left a comment
There was a problem hiding this comment.
Added a couple comments.
mschile
reviewed
Feb 4, 2026
mschile
approved these changes
Feb 4, 2026
…installed?" This reverts commit 6dea903.
349201b to
b608a9c
Compare
3506852 to
141cadd
Compare
scytacki
added a commit
to concord-consortium/starter-projects
that referenced
this pull request
Feb 5, 2026
- globals 16→17, wait-on 8→9, cross-env 7→10 - @stylistic/eslint-plugin 4→5, removed deprecated @stylistic/eslint-plugin-js and @stylistic/eslint-plugin-jsx sub-packages, migrated rule prefixes - eslint-plugin-jest 28→29, eslint-plugin-react-hooks 5→7 (updated to flat config format), eslint-plugin-cypress 4→5 - jest 29→30, jest-environment-jsdom 29→30, @types/jest 29→30 - cypress 14→15, @cypress/webpack-preprocessor 6→7 - Updated cypress-coverage.md to reflect current config file locations - Added docs/dependency-notes.md tracking @cypress/code-coverage Cypress.env() deprecation warning (awaiting upstream fix in cypress-io/code-coverage#972) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
6 tasks
Contributor
Author
|
@cursor review |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
|
🎉 This PR is included in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
BREAKING CHANGE:
@cypress/code-coverageconfiguration must now be placed underexposeinstead ofenvin your Cypress configuration.Migrate from
Cypress.env()toCypress.expose()This PR migrates
@cypress/code-coverage's configuration fromCypress.env()toCypress.expose()in response to the deprecation ofCypress.env()in Cypress v15.10.0.Cypress.env()will be removed in Cypress 16, necessitating this breaking change. For more details about why Cypress has deprecatedCypress.env(), see the official documentation on migrating fromCypress.env()toCypress.expose().What Changed
exposekey in your Cypress configuration, rather than theenvkey.Cypress.env()replaced withCypress.expose()Migration
Before:
After:
CLI usage:
Additional Changes
Impact
env.codeCoveragewill no longer workSee the migration guide in the README for detailed migration instructions.
Note
High Risk
Breaking API change that affects all consumers’ Cypress configuration and touches core coverage collection/reporting paths; incorrect
exposesetup could silently disable coverage or alter reporting behavior.Overview
Breaking change:
@cypress/code-coveragenow reads all runtime configuration (includingcodeCoverage,coverage, andsendCoverageBatchSize) fromCypress.expose()/config.exposeinstead ofCypress.env()/config.env, and sets thecodeCoverageTasksRegisteredflag viaconfig.expose.The plugin implementation is refactored to TypeScript across core modules (
lib/task,lib/task-utils,lib/common-utils) and middleware, adds a sharedlib/plugins.tsentrypoint, and updates backend coverage middleware to returnnullwhen coverage is unavailable.Test/CI plumbing is updated: CircleCI moves to newer Cypress orb and Node images, adds a
build-diststep gating matrix test-app verification and Windows runs, and repository Cypress e2e test scaffolding is removed in favor of the new unit-test setup; docs and example configs are updated to useexpose(including a new 3.x→4.x migration section), andtest-apps/*/package-lock.jsonis gitignored.Written by Cursor Bugbot for commit 2455c9b. This will update automatically on new commits. Configure here.