Skip to content

Update dependency cross-env to v10#293

Closed
renovate[bot] wants to merge 222 commits into
mainfrom
renovate/cross-env-10.x
Closed

Update dependency cross-env to v10#293
renovate[bot] wants to merge 222 commits into
mainfrom
renovate/cross-env-10.x

Conversation

@renovate

@renovate renovate Bot commented Jul 25, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
cross-env ^7.0.3^10.0.0 age confidence

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).

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.

Andrei Kvapil (kvaps) and others added 30 commits March 7, 2024 16:21
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Initializing the project
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Update kubebuilder to v3.14.0
Generated and wrote the most basic EtcdCluster custom resource.
See #9
Fixes from comments #15 
- Fix API group name for custom resources
- remove unnecessary comment lines
1. Union argument layers and copy source code.
2. Changed layers order final image for grow cache hit
fixes: #10

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
- Added basic validating and defaulting webhooks
- Added simple test for defaulting webhook
Controller now can successfully bootstrap etcd cluster :)

Controller creates Service, ConfigMap and StatefulSet based on
EtcdCluster CR
Only EmptyDir storage is supported
Initialized status is being set and updated
Proof that it works:
https://github.com/hiddenmarten/etcd-operator/pull/1

After that just changed the name of the label, to the easier one.
Update cluster Ready status according to StatefulSet status and update
ConfigMap cluster state to `existing` after first time STS is ready
fixes #24
fixes #23 
fixes #30

---------

Co-authored-by: Kirill Ilin <stitch14@yandex.ru>
Co-authored-by: Kirill Garbar <kirill@garbar.pro>
The auxiliary GH action to setup release drafts and update change log
accordingly. Configured with autolabeler, so the PRs will be labeled
according to the PR branch name and/or files changed:

| Branch name  | Files changed | Resulting label |
| ------------- | ------------- | ------------- |
| deps/*  |  | `dependencies`  |
| chore/*  |  | `chore`  |
| docs/* | **/*.md | `documentation` |
| enh/* |  | `enhancement` |
| feature/* |  | `feature` |
| fix/* |  | `bugfix` |
| bugfix/* |  | `bugfix` |
|  | /api/* | `api-change` |
|  | /internal/* | `controllers` |

Based on labels release draft will be updated with 'Features', 'Bug
Fixes' and 'Maintenance' categories which will include corresponding
PR's title.
It's also possible to manage release draft's version by applying
`major`, `minor` and `patch` labels on PR. By default the version will
be the next patch version after the last release, v0.0.1 if none.

---------

Signed-off-by: Artem Bortnikov <artem.bortnikov@telekom.com>
Explicit RW permissions for content and pull requests required, due to
repository settings, which grants to workflows only read permissions in
the repository for the contents and packages scopes.

- RW for content is required for release draft creation
(release-drafter).
- RW for pull-requests is required for adding labels to PRs
(auto-labeler).

Signed-off-by: Artem Bortnikov <artem.bortnikov@telekom.com>
in order to access cluster from clients using one IP we decided to use
ClusterIP Service
Created basic docs site and filled content for main pages
This is important when scaling cluster up for this operation to be zero down time
fixes #25
In case error happens during status update request, reconcile will not
be requeued. So, this call should be moved ouside `defer` function
fixes #36
Just an idea to create `CODEOWNERS` to automatically assign reviewers
when changing specific part of code.
Is there anybody who would like to keep informed about updates?

Aproove from codeowners is required to merge every specific change.
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from 0a7c315 to bf3b888 Compare September 2, 2025 11:54
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch 2 times, most recently from 20c8748 to a1d131e Compare September 29, 2025 17:44
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from a1d131e to 0949c95 Compare November 10, 2025 11:47
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from 0949c95 to 4b189ae Compare February 12, 2026 15:53
## Summary
- Replace deprecated `gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0` with
`quay.io/brancz/kube-rbac-proxy:v0.18.1`
- The GCR-hosted image became unavailable after March 18, 2025
- The new image is from the original upstream author (brancz)

Fixes #271

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Updated authentication proxy image to
quay.io/brancz/kube-rbac-proxy:v0.18.1 across deployment configs and
Helm chart values.

* **Documentation**
* API reference updated to mark numerous embedded and top-level fields
as optional, clarifying optionality for specs like replicas, storage,
security, TLS, metadata, and pod disruption settings.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from 4b189ae to f0f990c Compare March 13, 2026 10:10
@renovate renovate Bot changed the title Update dependency cross-env to v10 chore(deps): update dependency cross-env to v10 Mar 23, 2026
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from f0f990c to 13bbeb0 Compare March 23, 2026 16:58
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from 13bbeb0 to 878af3b Compare March 26, 2026 07:36
@renovate renovate Bot changed the title chore(deps): update dependency cross-env to v10 Update dependency cross-env to v10 Apr 8, 2026
myagkov.y.y and others added 3 commits April 16, 2026 22:37
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from 878af3b to 0dac2b5 Compare May 8, 2026 13:34
@renovate renovate Bot force-pushed the renovate/cross-env-10.x branch from 0dac2b5 to ee379d4 Compare May 19, 2026 07:19
Andrey Kolkov (androndo) and others added 3 commits May 22, 2026 12:52
* drop /bin/sh from restore: collapse restore-agent + restore-datadir
  into a single Go initContainer using etcdutl/v3/snapshot.NewV3()
* PodSecurityContext.FSGroup=65532 when bootstrap.restore is set so
  the nonroot restore-agent can mkdir into a freshly-mounted PVC
* tighten restore-agent: require all 5 env vars, trim cluster envs
  symmetrically, log + os.RemoveAll on partial state before retry,
  sentinel-based skip-check instead of bare member/
* bump default restore-agent memory limit (etcdutl Restore() runs
  in-process and OOM-kills on multi-GB snapshots at 512Mi)
* mirror PVC.SubPath hardening on the restore side (validatePVCSubPath)
* treat Job.Status.CompletionTime==nil in the errNoMarker grace
  branch as "still within grace" — finalize-empty is unrecoverable
* Go toolchain bump 1.22.4 -> 1.23.0 (Dockerfile + 5 workflows)
  required by go.etcd.io/etcd/etcdutl/v3 v3.5.21
* controller-gen bump v0.15.0 -> v0.16.5 (needed for Go 1.23 build);
  regenerate CRD + RBAC + deepcopy on top
* new CI workflow: codegen-drift gate runs make manifests generate
  helm-crd-copy and fails on dirty git status
* e2e: harden the kubectl port-forward race by wrapping health-
  check in Eventually; add restore continuation spec exercising the
  full PVC restore path against a live cluster

Signed-off-by: Andrey Kolkov <androndo@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.