Open slonka opened 1 year ago
Triage: have a linter to avoid links to the code. We shouldn't depend on linking to the code directly. If what we want is the list of supported k8s version we should likely pass that in versions.yaml like we do for EOL dates for example.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Description
Following a conversation from a review - https://github.com/kumahq/kuma-website/pull/1263#discussion_r1144364011 - it would be great to figure out how to automate these kinds of things. We could have a special directive that would go and fetch a particular line of kuma code. Something like this:
transform it and put it in the docs. So when we run this normally it would just use the saved value ("v1.26.1"), but when run with a special argument it would update the source code. Then we could have the update run on a cron job as a GHA.