Revise stable tag env strategy
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
Currently, the publish workflow tries to crawl the github releases api in order to obtain the latest stable. This is causing problems for our Linkerd CI pipeline because the latest released stable is quite far back in the list (more than the default 30 items returned).
I have bumped the returned items params on the API request, but this is only a temporary solution. One option is to hardcode the latest stable that has been released as presumably it would not change.
For context:
https://github.com/linkerd/website/pull/1842
https://github.com/linkerd/website/actions/runs/10826561944/job/30037781523
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the publish workflow and its GitHub releases API request, then review the linked website pull request and Linkerd CI job for the failure context. The work is done when the workflow reliably identifies the latest stable release without depending on the API's default 30-item result limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100