Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: Correct digest resolution when the replacementName and replacementVersion options are defined #27773 #28654

Closed
wants to merge 1 commit into from
Closed

fix: Correct digest resolution when the replacementName and replacementVersion options are defined #27773 #28654

wants to merge 1 commit into from

Conversation

ssegato81
Copy link
Contributor

Changes

  • The getDigestConfig variable uses the correct lookupName when it's running a replacement and the replacementName is set

Context

Closes #20304

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@ssegato81
The function the retrives the digest for a specific update now uses t…
b432cf0 
…he replacementName option when it's running a replacement
@ssegato81 ssegato81 closed this Apr 25, 2024
@ssegato81 ssegato81 deleted the fix/20304-replacementName branch April 25, 2024 13:50
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

docker: Replacement causes existing dependencies to use wrong digest
1 participant
@ssegato81