New issue
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
Dependabot gets confused over a directory name #9683
Labels
L: git:submodules
Git submodules
L: java:maven
Maven packages via Maven
L: ruby:bundler
RubyGems via bundler
T: bug 🐞
Something isn't working
Comments
github-actions
bot
added
L: git:submodules
Git submodules
L: java:maven
Maven packages via Maven
L: ruby:bundler
RubyGems via bundler
labels
May 7, 2024
This same problem is occurring on a different repository: https://github.com/io7m-com/quixote/network/updates/826262809
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
L: git:submodules
Git submodules
L: java:maven
Maven packages via Maven
L: ruby:bundler
RubyGems via bundler
T: bug 🐞
Something isn't working
Is there an existing issue for this?
Package ecosystem
Maven
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
https://github.com/io7m-com/xstructural/blob/develop/.github/dependabot.yml
Updated dependency
No response
What you expected to see, versus what you actually saw
See https://github.com/io7m-com/xstructural
My project contains the following modules:
Each one of these modules is a directory with a Maven
pom.xml
file in it. So for example, there's acom.io7m.xstructural.api/pom.xml
file, acom.io7m.xstructural.cmdline/pom.xml
file, and so on.Unfortunately, that last module seems to trip up Dependabot. It sees the filename
com.io7m.xstructural.xml
, apparently thinks "this is an XML file", tries to open it as a file, and immediately encounters an "is a directory" I/O error. This can be seen in the attached log output below.This essentially causes Dependabot to fail to provide any updates to the repository.
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
The text was updated successfully, but these errors were encountered: