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

Update dependency vite-tsconfig-paths to v5.1.4 #9902

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite-tsconfig-paths 5.1.3 -> 5.1.4 age adoption passing confidence

Release Notes

aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)

v5.1.4

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x-lockfile branch 13 times, most recently from 89472a1 to 94aae44 Compare December 12, 2024 00:09
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x-lockfile branch from 94aae44 to 3ce9053 Compare December 12, 2024 03:05
Copy link
Contributor

Code Coverage Report: Only Changed Files listed

Package Coverage
Overall Coverage 🟢 85%

Minimum allowed coverage is 0%, this run produced 85%

@renovate renovate bot merged commit 449fa27 into main Dec 12, 2024
15 checks passed
@renovate renovate bot deleted the renovate/vite-tsconfig-paths-5.x-lockfile branch December 12, 2024 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants