Skip to content

fix: remove pip ecosystem from Dependabot config#11

Draft
sickkick wants to merge 1 commit into
mainfrom
cursor/fix-dependabot-pip-errors-39f5
Draft

fix: remove pip ecosystem from Dependabot config#11
sickkick wants to merge 1 commit into
mainfrom
cursor/fix-dependabot-pip-errors-39f5

Conversation

@sickkick

@sickkick sickkick commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

Removes the pip package ecosystem from Dependabot configuration to fix daily workflow failures.

Problem

The Dependabot Updates workflow has been failing daily since June 12th with the error:

ERROR <job_...> Error during file fetching; aborting: No files found in /

This happens because Dependabot is configured to look for pip dependencies (like requirements.txt, setup.py, or pyproject.toml) but this repository doesn't have any Python dependency files.

Root Cause

This is a Home Assistant custom integration that:

  • Has no external PyPI dependencies (empty requirements array in manifest.json)
  • Manages dependencies through Home Assistant's native manifest.json format, not pip
  • Doesn't need a requirements.txt or similar file

Solution

Remove the pip ecosystem entry from .github/dependabot.yml. The github-actions ecosystem remains for updating action versions.

Testing

After merging, Dependabot will only run updates for GitHub Actions, and the daily pip update failures will stop.

Open in Web Open in Cursor 

This integration has no pip dependencies to manage - it's a Home Assistant
custom integration that manages dependencies through manifest.json instead.

The pip ecosystem configuration was causing daily failures because Dependabot
couldn't find any Python dependency files (requirements.txt, setup.py, etc.)
in the repository root.

Fixes the 'No files found in /' errors in Dependabot Updates workflow.

Co-authored-by: Michael Shaffer <sickkick40@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants