Skip to content

fix(deps): update dependency execa to v5.0.1 #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 31, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 31, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
execa 5.0.0 -> 5.0.1 age adoption passing confidence

Release Notes

sindresorhus/execa

v5.0.1

Compare Source


Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever PR becomes conflicted, 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 has been generated by WhiteSource Renovate. View repository job log here.

@github-actions github-actions bot added the type: bug code to address defects in shipped code label May 31, 2021
@renovate renovate bot merged commit 28df64f into main May 31, 2021
@renovate renovate bot deleted the renovate/execa-5.x-lockfile branch May 31, 2021 02:03
serhalp pushed a commit that referenced this pull request Apr 5, 2024
* perf: shim next's telemetry module to improve startup performance

* Update src/build/content/server.ts

Co-authored-by: Matt Kane <[email protected]>

* fix: don't break the build if failed to apply perf patch

* feat: also run on latest canaries

* test: setup next patching for tests

* test: refactor version checking a bit to allow canaries for ongoing always

* test: update var names in tests, make potential assertion failures more readable by checking object with version so failure would log version as well

* tmp: make minVersion lower to check that tests would suggest bumping it

* test: add test checking that patch is being applied and wether upper bound should be bumped

* test: normalize path for win32 (?)

* test: normalize path for win32 (vol2)

* fix: max version

* chore: specify type of patch in error message

---------

Co-authored-by: Matt Kane <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug code to address defects in shipped code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant