-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Document the new version option from the Symfony bin #12445
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
Conversation
$ symfony new my_project_name 3.1.5 | ||
|
||
# use a beta or RC version (useful for testing new Symfony versions) | ||
$ symfony new my_project 2.7.0-BETA1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BETA and RC does not work, I get Could not find package symfony/skeleton with version 3.4.0-RC1.
.
Even with more recent branches: Could not find package symfony/skeleton with version 4.3.0-BETA1.
I guess we need to tag the skeleton too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The special version values are lts
, stable
, next
, or previous
.
We already document lts
. I'm not sure about stable
because it's the one used when you don't specify the version, so better not complicate things. About previous
, I'm not sure either about documenting it in the docs. Finally, the next
value may be interesting because it allows you to early test whatever the next Symfony version will be.
|
||
# use a specific Symfony version | ||
$ symfony new my_project_name 2.8.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any version lower to 3.3 does not work because symfony/skeleton
did not exist (Could not find package symfony/skeleton with version 2.8.3.
).
@@ -31,15 +31,15 @@ to create files and execute the following commands: | |||
.. code-block:: terminal | |||
|
|||
$ cd projects/ | |||
$ symfony new blog 3.4 | |||
$ symfony new --version=3.4 blog |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps the version option would look better at the end than between the arguments ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think too but since there were already occurences like this in setup/symfony_server.rst
I continued.
…bin (fancyweb) This PR was merged into the 3.4 branch. Discussion ---------- Document the new version option from the Symfony bin `symfony new blog 3.4` results in `Incorrect usage: Too many arguments`. The version must now be specified with the `version` option. Commits ------- 1f2877f Document the new --version option from the Symfony bin
Thomas, thanks for taking care of this. As proposed by Yonel, while merging I changed the position of the |
symfony new blog 3.4
results inIncorrect usage: Too many arguments
. The version must now be specified with theversion
option.