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

Update abseil-cpp digest to aea2fc0 #128

Closed

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Feb 24, 2025

This PR contains the following updates:

Package Type Update Change
abseil-cpp git_override digest 4a2c633 -> aea2fc0

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot changed the title Update abseil-cpp digest to 52fa46a Update abseil-cpp digest to a290137 Feb 24, 2025
@renovate-bot renovate-bot force-pushed the renovate/abseil-cpp-digest branch from 15f86ef to b1d8bb0 Compare February 24, 2025 19:41
@renovate-bot renovate-bot changed the title Update abseil-cpp digest to a290137 Update abseil-cpp digest to e870ce0 Feb 25, 2025
@renovate-bot renovate-bot force-pushed the renovate/abseil-cpp-digest branch from b1d8bb0 to edac747 Compare February 25, 2025 02:14
@renovate-bot renovate-bot changed the title Update abseil-cpp digest to e870ce0 Update abseil-cpp digest to aea2fc0 Feb 25, 2025
@renovate-bot renovate-bot force-pushed the renovate/abseil-cpp-digest branch from edac747 to 5fa545c Compare February 25, 2025 18:46
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