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

fix(deps): update turbo monorepo to v1.10.9 #215

Merged
merged 1 commit into from
Jul 21, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 19, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-turbo 1.10.3 -> 1.10.9 age adoption passing confidence
turbo (source) 1.10.8 -> 1.10.9 age adoption passing confidence

Release Notes

vercel/turbo (eslint-config-turbo)

v1.10.9: Turborepo v1.10.9

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v1.10.8...v1.10.9

v1.10.8: Turborepo v1.10.8

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v1.10.7...v1.10.8

v1.10.7: Turborepo v1.10.7

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v1.10.6...v1.10.7

v1.10.6: Turborepo v1.10.6

Compare Source

What's Changed

Changelog

Full Changelog: vercel/turborepo@v1.10.5...v1.10.6

v1.10.5: Turborepo v1.10.5

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v1.10.4...v1.10.5

v1.10.4: Turborepo v1.10.4

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v1.10.3...v1.10.4


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 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.

@vercel
Copy link

vercel bot commented Jul 19, 2023

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

Name Status Preview Comments Updated (UTC)
chia1104 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 19, 2023 6:34pm
dash-chia1104 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 19, 2023 6:34pm

@railway-app
Copy link

railway-app bot commented Jul 19, 2023

This PR was not deployed automatically as @renovate[bot] does not have access to the Railway project.

In order to get automatic PR deploys, please add @renovate[bot] to the project inside the project settings page.

@@ -76,7 +76,7 @@
"shell-quote": "^1.8.1",
"superjson": "1.12.4",
"ts-node": "^10.9.1",
"turbo": "1.10.8",
"turbo": "1.10.9",
"typescript": "^5.1.3",
"vitest": "^0.33.0",
"zod": "^3.21.4"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code patch you provided seems to be a change in the specific versions of some dependencies in a Node.js project. Here is a brief code review:

  1. The change from "turbo": "1.10.8" to "turbo": "1.10.9" appears to update the version of the "turbo" dependency. Make sure to check the release notes or documentation for this dependency to see if there are any breaking changes or important bug fixes introduced in version 1.10.9.

  2. It's generally a good practice to keep your dependencies up to date, as newer versions often include bug fixes, security patches, and performance improvements. However, it's important to thoroughly test your code after updating dependencies to ensure compatibility and avoid introducing new issues.

  3. Apart from the specific version changes, I don't see any other code modifications in the provided patch. If there are additional changes in your codebase, please provide more information so that I can review them as well.

Overall, reviewing the code itself isn't possible without seeing the actual code. This patch only shows changes to dependency versions, which is generally considered a good practice to keep dependencies up to date. However, it's important to thoroughly test your code after updating dependencies to ensure everything works as expected.

turbo-linux-64: 1.10.9
turbo-linux-arm64: 1.10.9
turbo-windows-64: 1.10.9
turbo-windows-arm64: 1.10.9
dev: false

/tw-to-css@0.0.11(ts-node@10.9.1):
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code patch you provided appears to be related to dependency versions and resolutions. Here are the observations based on the given information:

  1. The turbo package is updated from version 1.10.8 to 1.10.9.
  2. There seem to be updates in various other packages as well, but they are not explicitly mentioned or visible in the patch.
  3. All platform-specific versions of turbo (e.g., turbo-darwin-64, turbo-linux-arm64, etc.) are also updated to version 1.10.9.
  4. The optionalDependencies field in the turbo package indicates that it depends on other platform-specific versions of turbo with the same updated version 1.10.9.

Overall, the code patch seems to update the turbo package and its corresponding platform-specific versions. It's generally a good practice to keep your dependencies up to date for bug fixes, security improvements, and new features.

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.

1 participant