Consider using changie for releases
Open
Nobody has claimed this yet.
area/build
kind/engineering
kind/postmortem-followup
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
This would make pulumi-java match pulumi-dotnet and pulumi-yaml, for a more consistent release process.
- #1928
- Update workflows to automatically tag the release
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
Compare the release workflows in pulumi-java with those in pulumi-dotnet and pulumi-yaml, then review how changie is used there. Identify the workflows that need updating so releases are tagged automatically; the issue is done when that unchecked workflow task is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100