Skip to content
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

⬆️ Upgrade Node.js to v18.17.1 #389

Merged
merged 1 commit into from
Aug 10, 2023
Merged

⬆️ Upgrade Node.js to v18.17.1 #389

merged 1 commit into from
Aug 10, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 9, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
node volta patch 18.17.0 -> 18.17.1
node (source) patch 18.17.0 -> 18.17.1

Release Notes

nodejs/node (node)

v18.17.1: 2023-08-09, Version 18.17.1 'Hydrogen' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes

The following CVEs are fixed in this release:

More detailed information on each of the vulnerabilities can be found in August 2023 Security Releases blog post.

Commits

Configuration

📅 Schedule: Branch creation - "after 9pm every weekday,before 6am every weekday,every weekend" in timezone Europe/Paris, 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 these updates again.


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

This PR has been generated by Mend Renovate. View repository job log here.

@jpolo jpolo added this pull request to the merge queue Aug 10, 2023
Merged via the queue into main with commit 8135d48 Aug 10, 2023
9 checks passed
@jpolo jpolo deleted the renovate/node-18.17.x branch August 10, 2023 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant