[CI] Lookup Release Version # When Manually Releasing
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 239
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 5
Description
While dispatching, if one of the steps here isn't dynamically identifying the latest release tag, we might want to require the release tag as input here.
You might like to grab the release tag lookup "function" from another one of the makefiles / workflows.
Originally posted by @leecalcote in https://github.com/layer5io/sistent/pull/95#discussion_r1323668544
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
Inspect the manually dispatched release workflow and compare its release-tag lookup with the other makefiles or workflows mentioned in the issue. Determine whether the latest release tag is identified dynamically or should be required as an input, then verify the manual release path uses the chosen behavior.
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
- Needs clarification
- Newbie friendliness
- 35/100