Missing some GitHub Releases
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by comparing the GitHub Releases page with the entries in CHANGELOG.md at the linked commit, especially lines 7–64, and determine which releases are missing. Check the repository's documented release process, if available; done means the missing releases are published or the issue clearly identifies the required release steps.
Written by the indexing model from the issue text.
Description
I just happened to notice that the latest GitHub Release is v0.12.78 but the Changelog shows many releases since then:
https://github.com/babashka/cli/blob/5fb411ecd08731616c549059e84cc57555a78e0d/CHANGELOG.md?plain=1#L7-L64
- Dominant language
- Clojure
- Stars
- 293
- Forks
- 22
- Avg merge
- 27m
- Merged PRs (30d)
- 12
Getting set up
We have not checked this project's setup files yet. 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.
Similar issues
-
.Frontend .Needs Triage .Team/UXWest Difficulty:Easy Priority:P3 Type:Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metabase/metabase#83008 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nasa/Common-Metadata-Repository#2502 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
clojure-emacs/cider#4203 ·