ci: use the docker-compose Dependabot ecosystem for the devcontainer - #8123
Conversation
The entry added in LibreSign#8033 used the docker ecosystem, which only reads Dockerfiles and Kubernetes manifests. /.devcontainer declares its images in docker-compose.yml, so every Dependabot job for it failed with "No Dockerfiles nor Kubernetes YAML found in /.devcontainer" and the nextcloud-dev image tag was never checked. Fixes LibreSign#8121 Assisted-by: Claude Code:claude-fable-5 Signed-off-by: André Maia <andrefnkmm@gmail.com>
|
/backport to stable35 |
|
/backport to stable34 |
|
/backport to stable33 |
|
/backport to stable32 |
|
The backport to # Switch to the target branch and update it
git checkout stable32
git pull origin stable32
# Create the new backport branch
git checkout -b backport/8123/stable32
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2bfe6288
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/8123/stable32Error: Failed to check for changes with origin/stable32: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # Switch to the target branch and update it
git checkout stable33
git pull origin stable33
# Create the new backport branch
git checkout -b backport/8123/stable33
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2bfe6288
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/8123/stable33Error: Failed to check for changes with origin/stable33: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # Switch to the target branch and update it
git checkout stable34
git pull origin stable34
# Create the new backport branch
git checkout -b backport/8123/stable34
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2bfe6288
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/8123/stable34Error: Failed to check for changes with origin/stable34: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # Switch to the target branch and update it
git checkout stable35
git pull origin stable35
# Create the new backport branch
git checkout -b backport/8123/stable35
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2bfe6288
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/8123/stable35Error: Failed to push branch backport/8123/stable35: remote: Invalid username or token. Password authentication is not supported for Git operations. Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
Resolves: #8121
📝 Summary
The Dependabot entry added in #8033 for
/.devcontaineruses thedockerecosystem, which only reads Dockerfiles and Kubernetes manifests. The devcontainer declares its images indocker-compose.yml, so every daily job failed withNo Dockerfiles nor Kubernetes YAML found in /.devcontainer(e.g. https://github.com/LibreSign/libresign/actions/runs/33188239975) and theghcr.io/librecodecoop/nextcloud-dev:8.3tag was never checked.This switches the entry to the dedicated
docker-composeecosystem. Nothing else changes.Side effect to be aware of: Dependabot will now also see
mariadb:10.6in the same file and may propose MariaDB updates. If major bumps are not wanted there, anignorerule formariadbwithupdate-types: ["version-update:semver-major"]can be added — I left it out to keep this PR to the fix, happy to add it if preferred.axllent/mailpit,redisandnextcloud-dev-nginx:latestcarry no version tag and are skipped.🧪 How to test
Dependabot version updates only run from the default branch, so this cannot be exercised from a fork PR. After merge, the next scheduled job should show up as
docker-compose in /.devcontainer(instead ofdocker in /.devcontainer) under Insights → Dependency graph → Dependabot, without the "No Dockerfiles" error, and open a PR whenever a newernextcloud-devtag exists.✅ Checklist
🤖 AI (if applicable)