Update ramsey/composer-install action to v2.3.1 #16
Conversation
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 contains the following updates:
v2->2.3.1Release Notes
ramsey/composer-install (ramsey/composer-install)
v2.3.1Compare Source
Fixed
To avoid the actions/cache deprecation notices, upgrade to
@v3or@3.0.0.v2.3.0Compare Source
Added
require-lock-fileinput that forces a build failure if acomposer.lockfile is not present. (#251)Fixed
--working-dirwhen looking up Composer's cache directory. This fixes "Filecomposer.jsoncould not be found in the current directory" errors when runningcomposer installin sub-directories or other non-standard locations. (#225, #233, #246, #247)v2.2.0Compare Source
Added
custom-cache-suffixoption to allow projects to provide their own cache-busting strategies without defining full custom cache keys (#239)v2.1.1Compare Source
Fixed
set-outputcommand for GitHub's recommended approach for output (#238)v2.1.0Compare Source
Added
composer updateif a lock file is not present, avoiding the warning that appears when runningcomposer installwithout a lock file.v2.0.5Compare Source
Fixed
v2.0.4Compare Source
Fixed
v2.0.3Compare Source
Fixed
v2.0.2Compare Source
Fixed
locked,highest, orlowestare passed fordependency_versions. In these cases, we always default tolocked.v2.0.1Compare Source
Fixed
composer.jsonand emit error message if it does not validate.Configuration
📅 Schedule: Branch creation - Every 3 hours, between 06:00 AM and 10:59 PM, Monday through Friday ( * 6-22/3 * * 1-5 ), Every 3 hours, between 12:00 PM and 11:59 PM, only on Sunday and Saturday ( * 12-23/3 * * 0,6 ) in timezone Europe/Amsterdam, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.