joao.dubas/clean-architecture
1
0
Fork 0
Code Issues 1 Pull Requests 5 Packages Projects Releases Wiki Activity

fix(deps): update dependency @types/node to v22.17.0 #109

Open
renovate-bot wants to merge 1 commits from renovate/node-22.x-lockfile into main
pull from: renovate/node-22.x-lockfile
merge into: joao.dubas:main
Conversation 0 Commits 1 Files Changed 2 +34 -34
renovate-bot commented 2025-07-19 01:17:54 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 22.16.4 -> 22.17.0 age confidence

Configuration

📅 Schedule: 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 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.

This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | [`22.16.4` -> `22.17.0`](https://renovatebot.com/diffs/npm/@types%2fnode/22.16.4/22.17.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fnode/22.17.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fnode/22.16.4/22.17.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration 📅 **Schedule**: 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 becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xODguMyIsInVwZGF0ZWRJblZlciI6IjQxLjQyLjUiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
renovate-bot added 1 commit 2025-07-19 01:17:55 +00:00
fix(deps): update dependency @types/node to v22.16.5
All checks were successful
continuous-integration/drone/pr Build is passing
Details
9b574e5f08
renovate-bot force-pushed renovate/node-22.x-lockfile from 9b574e5f08 to aea496896a 2025-07-22 20:15:46 +00:00 Compare
renovate-bot force-pushed renovate/node-22.x-lockfile from aea496896a to 1fff4956ac 2025-07-23 22:15:13 +00:00 Compare
renovate-bot changed title from fix(deps): update dependency @types/node to v22.16.5 to fix(deps): update dependency @types/node to v22.17.0 2025-07-29 15:15:11 +00:00
renovate-bot force-pushed renovate/node-22.x-lockfile from 1fff4956ac to 094589786e 2025-07-29 15:15:13 +00:00 Compare
All checks were successful
continuous-integration/drone/pr Build is passing
Required
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/node-22.x-lockfile:renovate/node-22.x-lockfile
git checkout renovate/node-22.x-lockfile
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot joao.dubas
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: joao.dubas/clean-architecture#109
No description provided.
Delete Branch "renovate/node-22.x-lockfile"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?