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

build(deps): update turbo monorepo to ^1.12.0 #3875

Merged
merged 1 commit into from
Jan 31, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 31, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-turbo (source) ^1.11.3 -> ^1.12.0 age adoption passing confidence
turbo (source) ^1.11.3 -> ^1.12.0 age adoption passing confidence

Release Notes

vercel/turbo (eslint-config-turbo)

v1.12.0: Turborepo v1.12.0

Compare Source

What's Changed

Docs
create-turbo
Examples
Changelog

New Contributors

Full Changelog: https://github.com/vercel/turbo/compare/v1.11.3...v1.12.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@renovate renovate bot enabled auto-merge (squash) January 31, 2024 02:18
@renovate renovate bot requested a review from ykzts January 31, 2024 02:18
Copy link

vercel bot commented Jan 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
shinju-date ✅ Ready (Inspect) Visit Preview Jan 31, 2024 0:47am
shinju-date-admin ✅ Ready (Inspect) Visit Preview Jan 31, 2024 0:47am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

1 participant