3.9.0: RPM package name changed again
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
The RPM packages had a -1 after the version before the 3.8.0 release (https://github.com/getsops/sops/issues/1266#issuecomment-1693345800), which wasn't there anymore for 3.8.x. But now with 3.9.0 it's back:
sops-3.9.0-1.aarch64.rpm
sops-3.9.0-1.x86_64.rpm
(https://github.com/getsops/sops/releases/tag/v3.9.0)
This is extremely frustrating for automated consumers of the releases such as the Ansible community.sops release, since this again broke its SOPS installation step.
Is there a way to fix the filename format somehow so it won't change again in the future?
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 RPM artifacts in the v3.8.x and v3.9.0 releases and trace the release packaging configuration that produces their filenames. Confirm the intended stable format and verify it in a release build so automated consumers receive consistent names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100