Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 14, 2025

This PR contains the following updates:

Package Change Age Confidence
nodemon (source) 3.1.10 -> 3.1.11 age confidence

Release Notes

remy/nodemon (nodemon)

v3.1.11

Compare Source


Configuration

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

🚦 Automerge: Enabled.

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.

@changeset-bot
Copy link

changeset-bot bot commented Nov 14, 2025

⚠️ No Changeset found

Latest commit: c26f054

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/nodemon-3.x branch 2 times, most recently from 528e332 to c6754bc Compare November 18, 2025 09:47
@renovate renovate bot force-pushed the renovate/nodemon-3.x branch from c6754bc to c26f054 Compare November 18, 2025 10:10
@sonarqubecloud
Copy link

@angrykoala angrykoala merged commit 0f010d7 into main Nov 18, 2025
10 checks passed
@angrykoala angrykoala deleted the renovate/nodemon-3.x branch November 18, 2025 10:45
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.

2 participants