We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo
No response
ruffle-rs/ruffle#17567 (comment) and ruffle-rs/ruffle#16835 (comment) were closed, when they shouldn't have been.
The text was updated successfully, but these errors were encountered:
Also affected:
Sorry, something went wrong.
I'm seeing this as well with NuGet dependencies
Dependabot has been failing to run for the past 2 days but when it fails, it closes the open PRs instead of leaving them:
Attached is the log from my most recent failed run dependabot_fail.log
(Both 690 and 696 were closed with the message Looks like these dependencies are no longer updatable, so this is no longer needed.)
Looks like these dependencies are no longer updatable, so this is no longer needed.
@dependabot recreate
I'm also seeing this issue with NuGet packages in a .NET Framework repository
No branches or pull requests
Is there an existing issue for this?
Package ecosystem
cargo
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
ruffle-rs/ruffle#17567 (comment) and ruffle-rs/ruffle#16835 (comment) were closed, when they shouldn't have been.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: