You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this deprecation, Dependabot will no longer run on legacy infrastructure, and instead all Dependabot jobs will run in GitHub Actions. Customers will be migrated automatically with no need for manual intervention on their part, and Dependabot jobs will not be interrupted.
Intended Outcome
This will allow customers greater insight into Dependabot jobs and logs, and allow them to leverage the GitHub Actions APIs to observe Dependabot jobs or use the result of those jobs to kick off other parts of their CI/CD. They will also be able to set up Dependabot to run on self-hosted runners in order to allow Dependabot to access private registries that are not available to the public internet.
How will it work?
Dependabot will continue to function as always, but will be running its jobs in GitHub Actions.
The text was updated successfully, but these errors were encountered:
This issue is being closed as outdated. For more information, please check out this Discussion post. Stay tuned for new additions to our refreshed public roadmap!
Summary
With this deprecation, Dependabot will no longer run on legacy infrastructure, and instead all Dependabot jobs will run in GitHub Actions. Customers will be migrated automatically with no need for manual intervention on their part, and Dependabot jobs will not be interrupted.
Intended Outcome
This will allow customers greater insight into Dependabot jobs and logs, and allow them to leverage the GitHub Actions APIs to observe Dependabot jobs or use the result of those jobs to kick off other parts of their CI/CD. They will also be able to set up Dependabot to run on self-hosted runners in order to allow Dependabot to access private registries that are not available to the public internet.
How will it work?
Dependabot will continue to function as always, but will be running its jobs in GitHub Actions.
The text was updated successfully, but these errors were encountered: