Skip to content

Deprecation Notice: Replace deprecated gaurav-nelson/github-action-markdown-link-check #12138

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

Open
Okabe-Junya opened this issue Apr 29, 2025 · 3 comments
Labels
area/ci Issues or PRs related to ci kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Okabe-Junya
Copy link
Member

/kind cleanup

Background

About two weeks ago, gaurav-nelson/github-action-markdown-link-check was marked as deprecated:

cf. https://github.com/gaurav-nelson/github-action-markdown-link-check

This repository is now ⛔️ deprecated and is no longer actively maintained.
For support and further development, please use the maintained fork available at Tcort GitHub Action Markdown Link Check.

Since this repository currently uses gaurav-nelson/github-action-markdown-link-check, we need to clean it up appropriately.

- uses: gaurav-nelson/github-action-markdown-link-check@3c3b66f1f7d0900e37b71eca45b63ea9eedfce31 # tag=1.0.17

- uses: gaurav-nelson/github-action-markdown-link-check@3c3b66f1f7d0900e37b71eca45b63ea9eedfce31 # tag=1.0.17

While the forked at tcort/github-action-markdown-link-check is suggested, it may still be too early to rely on that action.

Question:

How should we handle this deprecation in our workflow?

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 29, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Okabe-Junya
Copy link
Member Author

/area ci

@k8s-ci-robot k8s-ci-robot added the area/ci Issues or PRs related to ci label Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Issues or PRs related to ci kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants