operator-framework / operator-framework/java-operator-sdk
Improve Release - Proper Tagging
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
We discovered that during the release the tag that we create contains wrong version (the actual not the target release version), this does not make any functional problems, the code is the proper one, just the project version is set after GitHub Action receives the event, but the tag is already created that time.
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 by inspecting the GitHub Actions release workflow and the step that creates the project tag. Trace when the project version is updated relative to the release event, then verify that the created tag uses the target release version rather than the current version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100