Skip to content

Add Dependabot configuration for GitHub Actions updates #724

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

Closed
wants to merge 2 commits into from

Conversation

DanielAvdar
Copy link
Contributor

@DanielAvdar DanielAvdar commented May 15, 2025

Introduce a dependabot.yml file to automate dependency updates for GitHub Actions workflows. Updates are scheduled to run weekly, ensuring the project stays up-to-date with the latest changes.

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Introduce a dependabot.yml file to automate dependency updates for GitHub Actions workflows. Updates are scheduled to run weekly, ensuring the project stays up-to-date with the latest changes.

Signed-off-by: DanielAvdar <[email protected]>
@cclauss
Copy link
Contributor

cclauss commented May 18, 2025

@ihrpr
Copy link
Contributor

ihrpr commented May 23, 2025

Thank you for working on this!

We already have Dependabot Security Updates enabled though the github UI. We prefer to manage the rest of the decencies manually for this repo.

@ihrpr ihrpr closed this May 23, 2025
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.

3 participants