Make releasing more-defensive of errors. #1618
Conversation
|
@nathanhammond is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
| @@ -3,3 +3,5 @@ packages: | |||
| - "cli" | |||
| - "packages/*" | |||
| - "benchmark" | |||
| # Intentionally exclude the `npm` `turbo` package from the workspaces. | |||
There was a problem hiding this comment.
This is not "new" so-to-say. turbo only became a package very-recently, but because of how the native dependencies are generated this getting installed results in significant added complexity.
| cd $(CLI_DIR)/../scripts && ./await-publish.js | ||
| pnpm install --filter=turbo --ignore-scripts | ||
| git commit -anm "Update lockfile" | ||
|
|
There was a problem hiding this comment.
I never found a method to make this work which provided actual guarantees that a second request after a successful request to the registry would return the correct information.
They appear to have an "eventually consistent" model that makes this non-viable.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@mehulkar Actually, the way this PR configures it (removing it from the workspace), the lockfile doesn't contain the entries that were getting updated when When it's a workspace package, |
The 1.4.1 release demonstrated some gaps in the release process, this tests for error conditions before publishing, and removes the required lockfile dependency update.