Automate the release?
- Dominant language
- Java
- Stars
- 4.5k
- Forks
- 443
- Avg merge
- 5h 59m
- Merged PRs (30d)
- 77
Description
Pekko has this job:
https://github.com/apache/pekko/blob/main/.github/workflows/stage-release-candidate.yml
ASF Infra team and possibly Security team will have to approve issuing the GitHub secrets for Fory. You will notice some Pekko specific secrets in the job above.
It has really simplified the Pekko release process and we avoid issues where unstaged files can sneak into release artifacts.
Contributor guide
Research direction
Start by reading Pekko's .github/workflows/stage-release-candidate.yml and compare its release stages, Pekko-specific secrets, and approval requirements with Fory's current release process. Confirm the ASF Infra and possibly Security prerequisites before defining the workflow. Done means Fory can automate release-candidate staging while preventing unstaged files from entering release artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100