just release <service> <version>: file Release notes and tag
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start by reading the repository's just recipes and the release notes validation entry point mentioned in the issue. Trace how pending fragments are stored under unreleased and how release workflows use tags. Done means the command checks repository state, handles both mtg and services without release notes, creates the specified commit when needed, and creates a signed annotated tag without pushing; the issue says this will be checked by hand.
Written by the indexing model from the issue text.
Description
Parent
#175
What to build
A developer cuts a Release with one command, just release <service> <version> (e.g. just release mtg 0.57.0). The version is explicit, with no bump logic.
- It refuses when the tree is dirty, the branch is not
main, or the branch is behindorigin. - For mtg it runs the Release notes validation and refuses on an invalid pending fragment. It then moves the pending fragments from
unreleasedinto the new version folder, writesrelease.yamlwith the version and today's Release date, and commits as "mtg: release notes for v". With no pending notes it makes no commit. - It then creates the signed annotated tag
<service>/v<version>, and does not push. - Services without a release-notes directory are only tagged.
The existing tag-triggered release and deploy workflows stay unchanged.
Acceptance criteria
-
just release <service> <version>exists and is listed byjust - It refuses on a dirty tree, off
main, and when behindorigin, with a clear message - For mtg it refuses when a pending fragment is invalid (reusing the validation entry point)
- For mtg with pending notes: fragments are moved,
release.yamlis written, one commit "mtg: release notes for v" is made, then the signed annotated tagmtg/v<version>is created - For mtg without pending notes: no commit, only the tag
- For a service without release notes: only the tag
- Nothing is pushed
- Checked by hand on the first real Release (no automated test)
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 11h 20m
- Merged PRs (30d)
- 31
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 myOmikron/code
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 3/5 1-2 days Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
Similar issues
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ranxianglei/billion-context#4172 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
awslabs/threat-composer#362 ·
Maintainers usually reply within 1 day
-
Area/Cloud Needs Triage Type/Bug
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
wso2/product-integrator#2847 ·
Maintainers usually reply within 1 day