Dependabot job stuck in queued after FileUpdater failed error
blakehawkins opened this issue · comments
blakehawkins commented
Is there an existing issue for this?
- I have searched the existing issues
Package ecosystem
nuget
Package manager version
No response
Language version
dotnet6.0
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
updates:
- package-ecosystem: "nuget"
directory: "/"
schedule:
interval: "daily"
allow:
- dependency-name: "cx-*"
registries:
- nuget-org
- gh-packages
groups:
cx-group:
patterns:
- "cx-*"
registries:
nuget-org:
type: "nuget-feed"
url: "https://api.nuget.org/v3/index.json"
gh-packages:
type: "nuget-feed"
url: "https://nuget.pkg.github.com/firecatapult/index.json"
username: "x-access-token"
password: "${{ secrets.GH_PACKAGES_PAT }}"
Updated dependency
No response
What you expected to see, versus what you actually saw
Expected:
- job completes successfully after opening a PR. Job/action is then in a completed state, or if not then a warning state due to encountered errors
- Subsequent job starts on scheduled
- New job can be started manually by kicking the action
Actual:
- Job restarted into a queued state after hitting a FileUpdater error
- Queued job can't be cancelled with the cancel button
- New job can't be started
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue
No response