Skip to content

Migrate Away from Container Builder Token #69

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

Merged
merged 1 commit into from
Jul 14, 2025

Conversation

TylerKoon
Copy link
Contributor

Contents

In accordance with the impending migration away from CONTAINER_BUILDER_TOKEN, this PR:

  • Replaces usage of the CONTAINER_BUILDER_TOKEN with the BASE_CONTAINER_IMAGE_READER_DEPENDABOT token in dependabot configurations

Parent Issue: https://github.com/github/vuln-mgmt-eng/issues/5932

Copy link

Coverage report

This PR does not seem to contain any modification to coverable code.

@TylerKoon TylerKoon marked this pull request as ready for review July 14, 2025 16:32
@Copilot Copilot AI review requested due to automatic review settings July 14, 2025 16:32
@TylerKoon TylerKoon requested a review from a team as a code owner July 14, 2025 16:32
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR migrates away from the deprecated CONTAINER_BUILDER_TOKEN to the new BASE_CONTAINER_IMAGE_READER_DEPENDABOT token in dependabot configuration, following GitHub's impending migration requirements.

  • Updates the password reference in the docker-registry configuration for dependabot
  • Ensures compliance with the new token requirements for container image access

@TylerKoon TylerKoon merged commit 788bbf5 into main Jul 14, 2025
25 checks passed
@TylerKoon TylerKoon deleted the VME-5932-migrate-away-from-container-builder-token branch July 14, 2025 20:31
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