Update dependency cross-env to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cross-env	^5.2.0 → ^10.0.0

---

Release Notes

kentcdodds/cross-env (cross-env)

v10.1.0

Compare Source

Features

• add support for default value syntax (152ae6a)

For example:

"dev:server": "cross-env wrangler dev --port ${PORT:-8787}",

If PORT is already set, use that value, otherwise fallback to 8787.

Learn more about Shell Parameter Expansion

v10.0.0

Compare Source

TL;DR: You should probably not have to change anything if:

• You're using a modern maintained version of Node.js (v20+ is tested)
• You're only using the CLI (most of you are as that's the intended purpose)

In this release (which should have been v8 except I had some issues with automated releases 🙈), I've updated all the things and modernized the package. This happened in #​261

Was this needed? Not really, but I just thought it'd be fun to modernize this package.

Here's the highlights of what was done.

• Replace Jest with Vitest for testing
• Convert all source files from .js to .ts with proper TypeScript types
• Use zshy for ESM-only builds (removes CJS support)
• Adopt @​epic-web/config for TypeScript, ESLint, and Prettier
• Update to Node.js >=20 requirement
• Remove kcd-scripts dependency
• Add comprehensive e2e tests with GitHub Actions matrix testing
• Update GitHub workflow with caching and cross-platform testing
• Modernize documentation and remove outdated sections
• Update all dependencies to latest versions
• Add proper TypeScript declarations and exports

The tool maintains its original functionality while being completely modernized with the latest tooling and best practices

BREAKING CHANGES

• This is a major rewrite that changes the module format from CommonJS to ESM-only. The package now requires Node.js >=20 and only exports ESM modules (not relevant in most cases).

v7.0.3

Compare Source

Bug Fixes

• add maintenance mode notice (fe80c84)

v7.0.2

Compare Source

Reverts

• Revert "fix: signal handling (#​227)" (2a1f44c), closes #​227

v7.0.1

Compare Source

Bug Fixes

• signal handling (#​227) (8a9cf0e)

v7.0.0

Compare Source

Features

• update dependencies (#​223) (4ec6f40)

BREAKING CHANGES

• Drop Node 8 support

v6.0.3

Compare Source

Bug Fixes

• do not compile anything (67f21c3)

v6.0.2

Compare Source

Bug Fixes

• table of contents in README (a825e9c)

v6.0.1

Compare Source

Bug Fixes

• update all packages, tests, and README (36bb6c3)

v6.0.0

Compare Source

Bug Fixes

• bumped cross-spawn to version 7.0.0 (#​211) (61ebf59)

BREAKING CHANGES

• Drop support for Node.js < 7.

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • Between 04:00 PM and 07:59 PM, Monday through Friday (* 16-19 * * 1-5)
• Automerge
  • Between 02:00 PM and 06:59 PM, Monday through Thursday (* 14-18 * * 1-4)

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

♻ Rebasing: Whenever PR is behind base branch, 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: package-lock.json

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: ccd-case-activity-api@0.0.2
npm warn Found: chai@4.4.1
npm warn node_modules/chai
npm warn   dev chai@"^6.0.0" from the root project
npm warn   1 more (sinon-chai)
npm warn
npm warn Could not resolve dependency:
npm warn peer chai@"^4.0.0" from sinon-chai@3.7.0
npm warn node_modules/sinon-chai
npm warn   dev sinon-chai@"^3.5.0" from the root project
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-airbnb-base@14.2.1
npm error Found: eslint@9.39.4
npm error node_modules/eslint
npm error   dev eslint@"9.39.4" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.1
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@9.39.4
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^5.16.0 || ^6.8.0 || ^7.2.0" from eslint-config-airbnb-base@14.2.1
npm error node_modules/eslint-config-airbnb-base
npm error   dev eslint-config-airbnb-base@"^14.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@7.32.0
npm error node_modules/eslint
npm error   peer eslint@"^5.16.0 || ^6.8.0 || ^7.2.0" from eslint-config-airbnb-base@14.2.1
npm error   node_modules/eslint-config-airbnb-base
npm error     dev eslint-config-airbnb-base@"^14.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-20T15_45_40_151Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-20T15_45_40_151Z-debug-0.log

[hmcts-jenkins-a-to-c]

Plan Result (aat)

Plan: 0 to add, 1 to change, 0 to destroy.

• Update
  • module.redis-activity-service.azurerm_redis_cache.redis

Change Result (Click me)

  # module.redis-activity-service.azurerm_redis_cache.redis will be updated in-place
  ~ resource "azurerm_redis_cache" "redis" {
        id                                 = "/subscriptions/1c4f0704-a29e-403d-b719-b90c34ef14c9/resourceGroups/ccd-activity-service-cache-aat/providers/Microsoft.Cache/redis/ccd-activity-service-aat"
        name                               = "ccd-activity-service-aat"
        tags                               = {
            "application"         = "core-case-data"
            "autoShutdown"        = "true"
            "builtFrom"           = "https://github.com/HMCTS/ccd-case-activity-api.git"
            "businessArea"        = "CFT"
            "contactSlackChannel" = "#ccd-community"
            "environment"         = "staging"
            "managedBy"           = "CCD"
        }
        # (24 unchanged attributes hidden)

      ~ redis_configuration {
          ~ maxfragmentationmemory_reserved         = 125 -> 642
          ~ maxmemory_delta                         = 125 -> 642
          ~ maxmemory_reserved                      = 125 -> 642
            # (14 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

[hmcts-jenkins-a-to-c]

Plan Result (prod)

No changes. Your infrastructure matches the configuration.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.