chore: release#207
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
d054531 to
449c003
Compare
14b3fd8 to
ea66718
Compare
74e3fbe to
742ce9c
Compare
0ef288a to
40a15bb
Compare
571423f to
508774b
Compare
fe695b0 to
273ec64
Compare
920de06 to
ad6ae2e
Compare
a8c4312 to
5467ca3
Compare
34e09bb to
0676fc1
Compare
fb59fa2 to
866adca
Compare
3f5cd94 to
a920a2c
Compare
4b6f27c to
19f3403
Compare
c8a4447 to
28d2cbc
Compare
c44aee0 to
e2d1828
Compare
96f8fc6 to
b66d986
Compare
f7da508 to
82e18ae
Compare
4fb9ded to
cedc846
Compare
91bd287 to
e2c4bf0
Compare
Contributor
|
Deployment failed with the following error: |
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
create-vercel-shop@0.3.0
Minor Changes
cdecd0aThanks @blurrah! - Replace thecreate-next-appdelegation with a direct codeload tarball fetch ofapps/template, plus a<pm> installandgit init. Drops the flag-forwarding and pre-prompt ceremony that existed only to round-trip the project name through a subprocess. CLI surface is nowcreate-vercel-shop [name] [--no-template] [--use-pnpm|--use-npm|--use-yarn|--use-bun]; create-next-app passthroughs like--import-aliasare removed (the template's tsconfig already configures aliases).Patch Changes
2b0eb6fThanks @blurrah! - Prompt for the project name up front when none is passed, so plugin installs run in the right directory. Previously, omitting the project-name argument letcreate-next-appprompt interactively in its own subprocess; the CLI never learned the chosen name and tried to install plugins in the parent directory. Also reverts thenode_modulespost-scaffold check, which was checking the wrong path in the same scenario.