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 mikepenz/action-junit-report action to v5 #156

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 5, 2024

This PR contains the following updates:

Package Type Update Change
mikepenz/action-junit-report action major v4 -> v5

Release Notes

mikepenz/action-junit-report (mikepenz/action-junit-report)

v5

Compare Source

  • no changes

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, check this box

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

@renovate renovate bot force-pushed the renovate/mikepenz-action-junit-report-5.x branch from 69e36f8 to 9348e57 Compare November 5, 2024 06:29
@renovate renovate bot force-pushed the renovate/mikepenz-action-junit-report-5.x branch from 9348e57 to afd1370 Compare December 2, 2024 10:30
Copy link

sonarqubecloud bot commented Dec 2, 2024

@hypery2k hypery2k added this pull request to the merge queue Dec 20, 2024
Merged via the queue into develop with commit 6d6fec5 Dec 20, 2024
8 checks passed
@hypery2k hypery2k deleted the renovate/mikepenz-action-junit-report-5.x branch December 20, 2024 03: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.

1 participant