search

boxuk / wp-muplugin-loader

A drop-in MU Plugin loader for WordPress
MIT License
19 stars 4 forks source link

[DEPS]: Bump composer/composer from 2.6.3 to 2.7.4 #148

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps composer/composer from 2.6.3 to 2.7.4.

Release notes

Sourced from composer/composer's releases.

2.7.4

  • Fixed regression (Call to undefined method ProxyManager::needsTransitionWarning()) with projects requiring composer/composer in an pre-2.7.3 version (#11943, #11940)

As a side-note, requiring composer/composer is frowned upon and should really only be done in circumstances where it is absolutely necessary, and ideally you should talk to us first to see if we can't help avoid it or help by extracting some code in a smaller library.

2.7.3

  • BC Warning: Fixed https_proxy env var falling back to http_proxy's value, this is still in place but with a warning for now, and https_proxy can now be set empty to remove the fallback. Composer 2.8.0 will remove the fallback so make sure you heed the warnings (#11915)
  • Fixed show and outdated commands to remove leading v in e.g. v1.2.3 when showing lists of packages (#11925)
  • Fixed audit command not showing any id when no CVE is present, the advisory ID is now shown (#11892)
  • Fixed the warning about a missing default version showing for packages with project type as those are typically not versioned and do not have cyclic dependencies (#11885)
  • Fixed PHP 8.4 deprecation warnings
  • Fixed clear-cache command to respect the config.cache-dir setting from the local composer.json (#11921)
  • Fixed status command not handling failed download/install promises correctly (#11889)
  • Added support for buy_me_a_coffee in GitHub funding files (#11902)
  • Added hg support for SSH urls (#11878)
  • Fixed some env vars with an integer value causing a crash (#11908)
  • Fixed context data not being output when using IOInterface as a PSR-3 logger (#11882)

2.7.2

  • Added info about the PHP version when running composer --version (#11866)
  • Added warning when the root version cannot be detected (#11858)
  • Fixed plugins still being enabled in a few contexts when running as root (c3efff91f)
  • Fixed outdated --ignore ... still attempting to load the latest version of the ignored packages (#11863)
  • Fixed handling of broken symlinks in the middle of an install path (#11864)
  • Fixed update --lock still incorrectly updating some metadata (#11850, #11787)

Full Changelog: https://github.com/composer/composer/compare/2.7.1...2.7.2

2.7.1

Check the 2.7.0 release notes for common problems troubleshooting if you are experiencing issues after upgrading to Composer 2.7.x

Changelog

  • Added several warnings when plugins are disabled to hint at common problems people had with 2.7.0 (#11842)
  • Fixed diagnose auditing of Composer dependencies failing when running from the phar

2.7.0

Read the Composer 2.7 Release Announcement for more details on the release highlights and the security fix.

Common upgrade problems

  • If you see errors with missing commands (symfony-cmd: command not found) or other failures and you are relying on plugins and running Composer as root (for example when you use AWS ElasticBeanstalk), read composer/composer#11839
  • If you are using plugins and bitbucket pipelines, read composer/composer#11839
  • If you see Fatal error: Declaration of {some-class}::execute(...) must be compatible with Composer\Command\SomeCommand::execute(): int then whatever code is extending a Composer command needs to be updated to also add the int return type, see composer/composer#11843 for more details.

Complete Changelog

  • Security: Fixed code execution and possible privilege escalation via compromised vendor dir contents (GHSA-7c6p-848j-wh5h / CVE-2024-24821)
  • Changed the default of the audit.abandoned config setting to fail, set it to report or ignore if you do not want this, or set it via COMPOSER_AUDIT_ABANDONED env var (#11643)
  • Added --minimal-changes (-m) flag to update/require/remove commands to perform partial update with --with-dependencies while changing only what is absolutely necessary in transitive dependencies (#11665)

... (truncated)

Changelog

Sourced from composer/composer's changelog.

[2.7.4] 2024-04-22

  • Fixed regression (Call to undefined method ProxyManager::needsTransitionWarning()) with projects requiring composer/composer in an pre-2.7.3 version (#11943, #11940)

[2.7.3] 2024-04-19

  • BC Warning: Fixed https_proxy env var falling back to http_proxy's value, this is still in place but with a warning for now, and https_proxy can now be set empty to remove the fallback. Composer 2.8.0 will remove the fallback so make sure you heed the warnings (#11915)
  • Fixed show and outdated commands to remove leading v in e.g. v1.2.3 when showing lists of packages (#11925)
  • Fixed audit command not showing any id when no CVE is present, the advisory ID is now shown (#11892)
  • Fixed the warning about a missing default version showing for packages with project type as those are typically not versioned and do not have cyclic dependencies (#11885)
  • Fixed PHP 8.4 deprecation warnings
  • Fixed clear-cache command to respect the config.cache-dir setting from the local composer.json (#11921)
  • Fixed status command not handling failed download/install promises correctly (#11889)
  • Added support for buy_me_a_coffee in GitHub funding files (#11902)
  • Added hg support for SSH urls (#11878)
  • Fixed some env vars with an integer value causing a crash (#11908)
  • Fixed context data not being output when using IOInterface as a PSR-3 logger (#11882)

[2.7.2] 2024-03-11

  • Added info about the PHP version when running composer --version (#11866)
  • Added warning when the root version cannot be detected (#11858)
  • Fixed plugins still being enabled in a few contexts when running as root (c3efff91f)
  • Fixed outdated --ignore ... still attempting to load the latest version of the ignored packages (#11863)
  • Fixed handling of broken symlinks in the middle of an install path (#11864)
  • Fixed update --lock still incorrectly updating some metadata (#11850, #11787)

[2.7.1] 2024-02-09

  • Added several warnings when plugins are disabled to hint at common problems people had with 2.7.0 (#11842)
  • Fixed diagnose auditing of Composer dependencies failing when running from the phar

[2.7.0] 2024-02-08

  • Security: Fixed code execution and possible privilege escalation via compromised vendor dir contents (GHSA-7c6p-848j-wh5h / CVE-2024-24821)
  • Changed the default of the audit.abandoned config setting to fail, set it to report or ignore if you do not want this, or set it via COMPOSER_AUDIT_ABANDONED env var (#11643)
  • Added --minimal-changes (-m) flag to update/require/remove commands to perform partial update with --with-dependencies while changing only what is absolutely necessary in transitive dependencies (#11665)
  • Added --sort-by-age (-A) flag to outdated/show commands to allow sorting by and displaying the release date (most outdated first) (#11762)
  • Added support for --self combined with --installed or --locked in show command, to add the root package to the package list being output (#11785)
  • Added severity information to audit command output (#11702)
  • Added scripts-aliases top level key in composer.json to define aliases for custom scripts you defined (#11666)
  • Added IPv4 fallback on connection timeout, as well as a COMPOSER_IPRESOLVE env var to force IPv4 or IPv6, set it to 4 or 6 (#11791)
  • Added support for wildcards in outdated's --ignore arg (#11831)
  • Added support for bump command bumping * to >=current version (#11694)
  • Added detection of constraints that cannot possibly match anything to validate command (#11829)
  • Added package source information to the output of install when running in very verbose (-vv) mode (#11763)
  • Added audit of Composer's own bundled dependencies in diagnose command (#11761)
  • Added GitHub token expiration date to diagnose command output (#11688)
  • Added non-zero status code to why/why-not commands (#11796)
  • Added error when calling show --direct <package> with an indirect/transitive dependency (#11728)

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 6 months ago

Superseded by #149.