Skip to content

build: update dependency wait-on to v8 #31154

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 20, 2025

Conversation

angular-robot
Copy link
Collaborator

This PR contains the following updates:

Package Type Update Change
wait-on devDependencies major ^6.0.0 -> ^8.0.0

Release Notes

jeffbski/wait-on (wait-on)

v8.0.3

Compare Source

v8.0.2

Compare Source

Dependency updates:

v8.0.1

Compare Source

v8.0.0: - breaking change for http unix socket use

Compare Source

Updated for security vulnerabilities with [email protected] and braces.

Breaking change in using latest axios with a unix socket URL

As part of the axios update, the syntax for using a socket with an http URL in axios has changed so you must specify the protocol and server

For example:

http://unix:SOCKETPATH:http://server/foo/bar

instead of just using only the path (no protocol and no server)

http://unix:SOCKETPATH:/foo/bar

Due to this change, I have updated my tests, docs, bumped the major version.

v7.2.0

Compare Source

Update axios from 0.27.2 to latest 1.6.1 which fixes security vulnerability CVE-2023-45857.

Thanks @​AndrewMax for the PR #​147 and also for those that confirmed it.

v7.1.0

Compare Source

Update dependencies.

Add ability to specify timeout, httpTimeout, and tcpTimeout with a unit (ms, m, s, h), defaults to ms if not specified. Thanks @​ntkoopman

v7.0.1

Compare Source

Removed unnecessary eslint-plugin-standard. It was no longer needed since already included in another package.

v7.0.0

Compare Source

Updated dependencies:

  • minimist
  • eslint
  • minimatch
  • axios
  • mocha
  • rxjs

The update to latest mocha removed support for Node.js below 12.


Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

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

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 Renovate Bot.

See associated pull request for more information.
@angular-robot angular-robot requested a review from a team as a code owner May 19, 2025 21:02
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels May 19, 2025
@angular-robot angular-robot requested review from wagnermaciel and ok7sai and removed request for a team May 19, 2025 21:02
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels May 19, 2025
@alan-agius4 alan-agius4 added the target: rc This PR is targeted for the next release-candidate label May 19, 2025
@devversion devversion merged commit a3bcca5 into angular:main May 20, 2025
35 checks passed
@devversion
Copy link
Member

The changes were merged into the following branches: main, 20.0.x

devversion pushed a commit that referenced this pull request May 20, 2025
See associated pull request for more information.

(cherry picked from commit a3bcca5)
@angular-robot angular-robot deleted the ng-renovate/wait-on-8-x branch May 20, 2025 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants