Skip to content
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

Fix: Drop support for composer/composer:^1.0.0 #807

Merged
merged 1 commit into from
Nov 22, 2021
Merged

Conversation

localheinz
Copy link
Member

This pull request

  • drops support for composer/composer:^1.0.0

@codecov
Copy link

codecov bot commented Nov 22, 2021

Codecov Report

Merging #807 (74bdd25) into main (13f1aca) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##               main     #807   +/-   ##
=========================================
  Coverage     83.96%   83.96%           
  Complexity       57       57           
=========================================
  Files             4        4           
  Lines           237      237           
=========================================
  Hits            199      199           
  Misses           38       38           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13f1aca...74bdd25. Read the comment docs.

@localheinz localheinz merged commit 30430f3 into main Nov 22, 2021
@localheinz localheinz deleted the fix/composer branch November 22, 2021 09:42
@localheinz
Copy link
Member Author

@szepeviktor

Shouldn't be a problem - when running

composer self-update --1

followed by

composer require --dev ergebnis/composer-normalize

then ergebnis/composer-normalize:^2.15.0 will be installed.

By the way, composer also emits a warning, suggesting to upgrade to composer/composer:^2.0.0:

Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants