composer
Dependency Dashboard
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.
This repository currently has no open or pending branches.
Detected Dependencies
dockerfile (3)
1.10/Dockerfile (1)
php 8-alpine2.2/Dockerfile (1)
php 8-alpinelatest/Dockerfile (1)
php 8-alpine
github-actions (4)
.github/workflows/1.10.yaml (17)
actions/checkout v6docker/metadata-action v5docker/metadata-action v5actions/checkout v6docker/setup-qemu-action v3docker/setup-buildx-action v3docker/login-action v3docker/login-action v3docker/login-action v3docker/build-push-action v6docker/build-push-action v6actions/upload-artifact v6actions/download-artifact v7docker/setup-buildx-action v3docker/login-action v3docker/login-action v3docker/login-action v3.github/workflows/2.2.yaml (17)
actions/checkout v6docker/metadata-action v5docker/metadata-action v5actions/checkout v6docker/setup-qemu-action v3docker/setup-buildx-action v3docker/login-action v3docker/login-action v3docker/login-action v3docker/build-push-action v6docker/build-push-action v6actions/upload-artifact v6actions/download-artifact v7docker/setup-buildx-action v3docker/login-action v3docker/login-action v3docker/login-action v3.github/workflows/latest.yaml (17)
actions/checkout v6docker/metadata-action v5docker/metadata-action v5actions/checkout v6docker/setup-qemu-action v3docker/setup-buildx-action v3docker/login-action v3docker/login-action v3docker/login-action v3docker/build-push-action v6docker/build-push-action v6actions/upload-artifact v6actions/download-artifact v7docker/setup-buildx-action v3docker/login-action v3docker/login-action v3docker/login-action v3.github/workflows/shellcheck.yaml (1)
actions/checkout v6
regex (2)
2.2/Dockerfile (1)
composer/composer 2.2.25latest/Dockerfile (1)
composer/composer 2.9.2
- [ ] Check this box to trigger a request for Renovate to run again on this repository
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
@alcohol I think there's a way to trigger the PR's automatically by changing the config but right now it's manual from this issue.
You can also see what assets it's currently configured on.
Not sure I understand the error here. The 2.2 branch does not relate to the version mentioned (2.8.9)?
Thanks for fixing that, totally didn't think that another rule would need to be added to explicitly disable those for that file.
Found out you can create a branch called renovate/<something> which would run the configuration to show if its valid or not.
Could prob simply those rules to:
"packageRules": [
{
"description": "Disables major and minor updates for composer/composer in 2.2",
"matchFileNames": [
"2.2/Dockerfile"
],
"matchPackageNames": [
"composer/composer"
],
"matchUpdateTypes": [
"major",
"minor"
],
"enabled": false
},
{
"description": "Configures updates for composer/composer in 2.2",
"matchFileNames": [
"2.2/Dockerfile"
],
"matchPackageNames": [
"composer/composer"
],
"matchUpdateTypes": [
"patch"
],
"commitMessageSuffix": " (2.2)",
"additionalBranchPrefix": "2.2-"
},
{
"description": "Configures updates for composer/composer in latest",
"matchFileNames": [
"latest/Dockerfile"
],
"matchPackageNames": [
"composer/composer"
],
"commitMessageSuffix": " (Latest)",
"additionalBranchPrefix": "latest-"
}
],
Which removes the explicit enable and unrequired
{
"matchPackageNames": [
"composer/composer"
],
"enabled": true
},
Yeah that sounds good to me. Feel free to submit a PR. Otherwise I will try to pick it up sometime next week.