oskoperator / oskoperator/osko
release-drafter publishes its unedited template
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 3
- Avg merge
- 44m
- Merged PRs (30d)
- 7
Description
On the 0.0.21 tag push, release-drafter published v0.0.21 automatically with its raw template body — including the literal placeholder **[Human readable summary of changes]**. #153 appeared twice because it carries both bug and documentation labels.
Earlier the same config produced a draft named vmain with tag_name: main: $RESOLVED_VERSION failed to resolve because the most recent releases are chart-releaser's osko-* and osko-crds-* tags, which are not semver-parseable.
Two decisions needed: whether the drafter should publish at all rather than leave a draft for editing, and how to stop the chart tags interfering with version resolution.
Contributor guide
No contributing guide indexed for this repository
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 by inspecting the release-drafter configuration and the chart-releaser tag flow described in the issue. Reproduce the 0.0.21 and vmain outcomes, then determine how publication behavior and version resolution should be configured; done means releases no longer contain raw placeholders or resolve to chart-related tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100