Release workflow: pre-releases must not become latest
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, github-actions, javascript, markdown
- Domain
- devops, documentation, release
Research direction
Start by reading the repository’s release.yml workflow and the README release instructions; the issue names no test files or additional entry points. Check how tag names determine image tags and GitHub release settings, then verify the documented release candidate steps. Done means prerelease tags publish only their versioned image and are marked as prereleases, while plain version tags retain today’s behavior.
Written by the indexing model from the issue text.
Description
release.yml runs on every vX.Y.Z tag. A pre-release such as v1.0.0-rc.1 would be published as ghcr.io/solidgeeks/strata:latest, so everyone running docker compose pull would get a release candidate.
Done when
- A tag with a pre-release part (
-rc.1,-beta.2…) publishes the image under its version only, neverlatest - Its GitHub release is marked as a pre-release
- Plain
vX.Y.Ztags behave as today (version,latest, signed, release notes) - The README explains how to try a release candidate
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 14m
- Merged PRs (30d)
- 31
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from SolidGeeks/strata
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SolidGeeks/strata#21 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
SolidGeeks/strata#22 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
SolidGeeks/strata#20 ·
Maintainers usually reply within 1 day
All issues in SolidGeeks/strata
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
account: profile bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 5 days
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/cozy-client#1777 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
NanmiCoder/dsh-agent-teams#326 ·
Maintainers usually reply within 1 day
-
[guide] AGENTS.md claims the coverage gate, e2e and full lint run on every PR after ADR 0011 focused validationPossibly taken @hivecommons-hive claimed this today. Openagent/guide documentation hive/claimed-by-guide stage/040-covered-by-pr
Difficulty 2/5 1-3 hours Newbie friendliness 81/100
cncf/endusers#2006 · 1 comment ·
Maintainers usually reply within 1 day