Skip to main content

Configuring Dependabot on GitHub-hosted runners

Enable Dependabot on GitHub-hosted runners to more easily identify Dependabot job errors and manually detect and troubleshoot failed runs.

谁可以使用此功能?

组织所有者和存储库管理员

Enabling or disabling Dependabot on standard GitHub-hosted runners

You can configure Dependabot on standard GitHub-hosted runners:

If you restrict access to your organization's or repository's private resources, you may need to update your list of allowed IP addresses prior to enabling Dependabot on GitHub Actions runners. You can update your IP allow list to use the GitHub-hosted runners IP addresses (instead of the Dependabot IP addresses), sourced from the meta REST API endpoint.

警告

You should not rely on the GitHub Actions IP addresses for authentication to private registries. These GitHub Actions addresses are not only used by GitHub, and should not be trusted for authentication. Instead, use a self-hosted runner to ensure greater control over your network access. For more information, see Configuring Dependabot on self-hosted runners.

For your repository

  1. 在 GitHub 上,导航到存储库的主页面。

  2. 在仓库名称下,单击 “Settings”****。 如果看不到“设置”选项卡,请选择“”下拉菜单,然后单击“设置”。

    存储库标头的屏幕截图,其中显示了选项卡。 “设置”选项卡以深橙色边框突出显示。

  3. 在边栏的“Security”部分中,单击“ Advanced Security”****。

  4. Under "Dependabot", to the right of "Dependabot on Actions runners", click Enable to enable the feature or Disable to disable it.

    注意

    Dependabot on GitHub Actions relies on the ubuntu-latest label to select the appropriate runner. To ensure Dependabot runs on GitHub-hosted runners, you should not use the label ubuntu-latest for self-hosted runners.

For your organization

Only repositories meeting the following criteria will be updated to run Dependabot on GitHub Actions the next time a Dependabot job is triggered.

  • Dependabot is enabled in the repository.
  • GitHub Actions is enabled in the repository.

If a repository in your organization has Dependabot enabled but GitHub Actions disabled, Dependabot will not run on GitHub Actions, but will continue to run using the built-in Dependabot application.

  1. 在 GitHub 的右上角,单击个人资料图片,然后单击“ Your organizations”****。

  2. 在组织旁边,单击“设置”。

  3. 在边栏的“Security”部分中,依次单击“ Advanced Security”和“Global settings”********。

  4. In the "Dependabot" section, next to "Runner type", confirm that you have selected "Standard GitHub runner". If not, click and update your configuration.

    注意

    Dependabot on GitHub Actions relies on the ubuntu-latest label to select the appropriate runner. To ensure Dependabot runs on GitHub-hosted runners, you should not use the label ubuntu-latest for self-hosted runners.

Enabling or disabling Dependabot on 大型运行器

If you run into Dependabot timeouts and out-of-memory errors, you may want to use 大型运行器, as you can configure these runners to have more resources. You can only enable 大型运行器 for Dependabot for an organization.

  1. Add a 大型运行器 to your organization and ensure the name specified is dependabot. For more information, see 管理较大的运行器.

  2. Opt in the organization to self-hosted runners. For more information, see Configuring Dependabot on self-hosted runners. This step is required, as it ensures that future Dependabot jobs will run on the larger GitHub-hosted runner that has the dependabot name.

    注意

    Dependabot on GitHub Actions relies on the ubuntu-latest label to select the appropriate runner. To ensure Dependabot runs on GitHub-hosted runners, you should not use the label ubuntu-latest for self-hosted runners.