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(docs): update deps/renovate digest to ff99265 #567

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 22, 2025

This PR contains the following updates:

Package Update Change
deps/renovate digest e3a4aaf -> ff99265

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 renovate bot enabled auto-merge (squash) January 22, 2025 13:15
Copy link
Contributor Author

renovate bot commented Jan 22, 2025

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot changed the title chore(docs): update deps/renovate digest to a6151da chore(docs): update deps/renovate digest to ff99265 Jan 22, 2025
@renovate renovate bot force-pushed the renovate/deps-renovate-digest branch from 185e142 to de9b160 Compare January 22, 2025 15:15
@renovate renovate bot merged commit f5a67aa into main Jan 22, 2025
3 of 4 checks passed
@renovate renovate bot deleted the renovate/deps-renovate-digest branch January 22, 2025 15:17
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