chore(turbo): include schema in turbo package #9714
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tknickman
approved these changes
Jan 17, 2025
This was referenced Jan 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a new
@turbo/types#copy-schematask which will copy the current schema intopackages/turbo. We do this since we explicitly exclude theturbopackage from our workspace so it's easier to have this hang off of@turbo/types.We then add this task to the
buildtarget which is a dependency of thepublish-turbotarget which is what gets run on release: https://github.com/vercel/turborepo/actions/runs/12796720464/job/35678219119#step:11:2Resolves #7466
Testing Instructions
Do a test run of the release and make sure we end up running the new
copy-schematask. Started here, will take a sec to get to the point in the release where we hit this codepath.You can see schema gets copied into the
turbopackage here