Use all cores for Turbo builds

[steveluscher]

I like using all 48 cores for these. How about you folks?

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9736796

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

[steveluscher]

• Use all cores for Turbo builds #2799 👈
• chore: update to Turborepo 2.0.4-canary.2 #2804
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @steveluscher and the rest of your teammates on Graphite

[steveluscher]

The other option is that we leave this the way it is (defaults to 10 cores) and I can just get used to writing --concurrency=100% when I run steps locally.

[buffalojoec]

The other option is that we leave this the way it is (defaults to 10 cores) and I can just get used to writing --concurrency=100% when I run steps locally.

Do you even alias bro?

[buffalojoec]

[github-actions]

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.