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 thollander/actions-comment-pull-request action to v3 #11

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 12, 2024

This PR contains the following updates:

Package Type Update Change
thollander/actions-comment-pull-request action major v2 -> v3

Release Notes

thollander/actions-comment-pull-request (thollander/actions-comment-pull-request)

v3

Compare Source


Configuration

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

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

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 added the renovate label Oct 12, 2024
@renovate renovate bot requested a review from a team as a code owner October 12, 2024 01:54
Copy link

PR checklist

Checklist:

  • Is the name of this app/solution still Automation Analyzer?
  • Have you updated the version tag in each .qvf file, and followed semantic versioning (e.g. v1.1.1)?
  • Is this PR named appropriately? For example:
    • Feature release: feat: add sheet usage event
    • Bug fix: fix: replaced deprecated events
    • Documentation update: docs: updated images in install guide
  • Have you reviewed the unbuilt diff generated by the workflow in /diff?

If you wish to merge and release:

  • Have this PR approved by a code owner, then merge into main
  • Go to releases, an action will generate a draft release with all files in /assets, and any external assets references in release.json
  • Make any updates, then submit the release

Common issues:

  • After merging, draft release doesn't update - this is usually because
    the action failed due to an old draft release with the same name.
    Delete the draft release, and re-run the action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants