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

feat(github-action)!: Update lycheeverse/lychee-action action to v2 #113

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
lycheeverse/lychee-action action major v1 -> v2

Release Notes

lycheeverse/lychee-action (lycheeverse/lychee-action)

v2

Compare Source


Configuration

📅 Schedule: Branch creation - "on saturday" in timezone Europe/Paris, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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/lycheeverse-lychee-action-2.x branch from 74e31f5 to cc46a19 Compare October 14, 2024 10:19
@renovate renovate bot force-pushed the renovate/lycheeverse-lychee-action-2.x branch from cc46a19 to 4d34abc Compare November 7, 2024 17:15
| datasource  | package                   | from | to |
| ----------- | ------------------------- | ---- | -- |
| github-tags | lycheeverse/lychee-action | v1   | v2 |
@renovate renovate bot force-pushed the renovate/lycheeverse-lychee-action-2.x branch from 4d34abc to 904003c Compare December 19, 2024 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants