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.

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

chore(deps): update docker.io/python digest to db0f388 - autoclosed #311

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 10, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
docker.io/python final digest 42aa835 -> db0f388

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 2830463277

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 0.0%

Totals Coverage Status
Change from base Build 2829965115: 0.0%
Covered Lines: 0
Relevant Lines: 0

πŸ’› - Coveralls

@renovate renovate bot changed the title chore(deps): update docker.io/python digest to db0f388 chore(deps): update docker.io/python digest to db0f388 - autoclosed Aug 10, 2022
@renovate renovate bot closed this Aug 10, 2022
@renovate renovate bot deleted the renovate/docker.io-python-digest branch August 10, 2022 11:54
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.

None yet

1 participant