[BUMP] Update dependency @badeball/cypress-cucumber-preprocessor to v26 (e2e)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@badeball/cypress-cucumber-preprocessor	^23.0.0 → ^26.0.0

---

Release Notes

badeball/cypress-cucumber-preprocessor (@​badeball/cypress-cucumber-preprocessor)

v26.0.0

Compare Source

Breaking changes:

• Remove flag to turn expectation errors soft. This feature was

  1. Overly complicated implementation-wise
  2. Likely not adopted widely, albeit I'm unsure
  3. Difficult to test properly
  • With the recent breaking changes made to Cypress, the following changes to this library would make it even more so. Thus, I am removing this feature for now.

Other changes:

• Add support for Cypress v15.18.0, fixes #​1358.

• Handle more corner cases related to reload-behavior, fixes #​1161.

• Handle even more corner cases related to reload-behavior, fixes #​1362.

v25.0.0

Compare Source

Breaking changes:

• Tags are no longer configurable using capital "TAGS", ie. cypress run -e TAGS=@​foo, only lowercase.

• Updated peer dependencies to exclude Cypress v15.18.0.

  • This version introduced a breaking change, which makes it currently unsupported.

  • The above-mentioned version will hopefully be fully supported in the near future.

v24.0.1

Compare Source

• Update dependency @​cucumber/pretty-formatter to v3.

  • This is not a breaking change, but warrants mentioning because the output is changed stylistically in some ways.

• Correctly handle edge case related to reload-behavior with run hooks, fixes #​1344.

v24.0.0

Compare Source

Breaking changes:

• Removed support for using browserify as a bundler.

  • Browserify is largely unmaintained at this point and is making it impossible to keep dependencies up-to-date as Browserify itself does not do that. Furthermore, the Browserify bundler is deprecated by Cypress. If you'd still like to use Browserify, you can pin your dependency on @badeball/cypress-cucumber-preprocessor to ~23.x.y.

  • A branch named v23.x.y has been created to continue illustrating how to use Browserify. This is mentioned in the FAQ.

• Bump node requirement slightly from v20.0.0 to ^20.12.0, ^21.7.0 or >=22.

  • This is in preperation of replacing chalk with util.styleText.

Other changes:

• Run hooks (BeforeAll/AfterAll) may now be optionally named. This is in line with how cucumber-js behaves.

• Allow step hooks to return skipped / pending.

  • This is similar to how steps themselves can also return the above mentioned literals. This is in line with how cucumber-js behaves.

• Attachments (using log(), link() or attach()) can be added in test run hooks (BeforeAll/AfterAll). This is in line with how cucumber-js behaves.

• Remove use of patch-package in development mode, which was causing some issues, closes #​1255.

• Add rudimentary support for videos in reports (messages & HTML), fixes #​1139.

  • This can be enabled by setting attachments.addVideos to true.

  • Videos, as with screenshots, are base64-encoded inline within the reports, making them bigger. I suspect size might be an issue for large attachments and this is why I consider this to be rudimentary to begin with. As issues arise, options to externalize attachments might be considered.

v23.2.1

Compare Source

• Determine interactive mode correctly, fixes #​1323.

v23.2.0

Compare Source

• Add a flag to turn expectation errors soft. Relates to #​1313 and #​1222.

  • During creation of message reports, which the JSON & HTML reports are products of, some test state is tracked by this library. This requires taking into account a myriad of edge cases, mostly related to Cypress' reload behavior. There are however likely several remaining edge cases that are unaccounted for.

    In case of #​1222, the fail fast strategy adopted here appeared to mask an underlying issue. I suspect this might also be the case for #​1313 and similar issues. Thus an option for erroring softly is introduced. With this option, instead of throwing fast in Cypress' event handlers, the preprocessor will emit an error message to stderr at the end of a run.

    My hope is that this will make it easier for the end-user to provide proper reproducible examples when running into these errors. Additionally, it can be useful for users whom which reports aren't strictly a necessity but do encounter such errors.

    This option can be configured similar to other options, with examples shown below.

    // package.json
    {
      "dependencies": {
        "@​badeball/cypress-cucumber-preprocessor": "latest"
      },
      "cypress-cucumber-preprocessor": {
        "state": {
          "softErrors": true
        }
      }
    }
    

    // .cypress-cucumber-preprocessorrc.json
    {
      "state": {
        "softErrors": true
      }
    }
    

    $ cypress run -e stateSoftErrors=true
    

    $ env CYPRESS_stateSoftErrors=true cypress run
    

v23.1.0

Compare Source

• Bumb engine requirement to Node v20.

  • This was accidentally left out during release of v23.0.0, where dropped support for v18 was announced. Due to the announcement, I don't consider this to be another breaking change.

• Expand type signature of scenario and step hooks, to allow tags to be defined using pure string arguments. This is in line with how cucumber-js behaves.

• Add support for attachments with filenames. This is in line with how cucumber-js behaves.

• Implement log, as seen in cucumber-js.

• Implement link, as seen in cucumber-js.

• Minor changes to the messages report, to ensure compatibility with cucumber-js.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every 1 hour every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: high-level-tests/e2e/package-lock.json

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm-run-all2@9.0.1
npm ERR! notsup Not compatible with your version of node/npm: npm-run-all2@9.0.1
npm ERR! notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0","npm":">= 10"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v24.15.0"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-20T12_46_44_458Z-debug-0.log

[pix-bot-github]

Choisir les applications à déployer :

• API | 👩‍💻 Dashboard Scalingo
• App (.fr) – App (.org) | 👩‍💻 Dashboard Scalingo
• Orga (.fr) – Orga (.org) | 👩‍💻 Dashboard Scalingo
• Certif (.fr) – Certif (.org) | 👩‍💻 Dashboard Scalingo
• Junior | 👩‍💻 Dashboard Scalingo
• Admin | 👩‍💻 Dashboard Scalingo
• API MaDDo | 👩‍💻 Dashboard Scalingo
• Audit Logger | 👩‍💻 Dashboard Scalingo

Important

N'oubliez pas de déployer l'API pour pouvoir accéder aux fronts et/ou à l’API MaDDo.