-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Should I Update composer #8901
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior (or desired behavior if a feature request)
When Upgrading Snipe-IT it should work without warnings/info
Actual Behavior
I get a info of a new composer Version:
Step 6: Updating composer dependencies:
(This may take a moment.)
√ Local composer.phar detected, so we'll use that.
-- Updating local composer.phar
A new stable major version of Composer is available (2.0.8), run "composer self-update --2" to update to it. See also https://getcomposer.org/2
You are already using composer version 1.10.19 (1.x channel).
Please confirm you have done the following before posting your bug report:
Provide answers to these questions:
storage/logs
and your webserver's logs. -> /Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.
https://snipe-it.readme.io/docs/getting-help
The text was updated successfully, but these errors were encountered: