Missing some GitHub Releases

I just happened to notice that the latest GitHub Release is v0.12.78 but the Changelog shows many releases since then:

Lines 7 to 64 in 5fb411e

    
           ## 0.12.91 
        
           - zsh completion: disable sorting for registered program names to preserve candidate order 
        
           ## 0.12.90 
        
           - `dispatch`: add `:supplied` to the opts map's `:org.babashka/cli` metadata with the set of option keys given on the command line 
        
           ## 0.12.89 
        
           - [#244](https://github.com/babashka/cli/issues/244): use metadata and docstrings from `:fn` and `:exec-fn` vars in babashka and ClojureDart 
        
           ## 0.12.88 
        
           - [#219](https://github.com/babashka/cli/issues/219): `:cmd-aliases` on a table entry or tree node gives a command one or more alternative names. 
        
           - A short option that declares a non-boolean `:coerce` takes the rest of its token as its value, like getopt: `-J-Dfoo=bar` binds `"-Dfoo=bar"`, `-p80` binds `80`. One leading `=` is stripped, like `--foo=bar`. Flag letters may precede the valued option in a cluster: with `:b` a flag and `:a` valued, `-ba x` parses as `-b -a x` 
        
           - [#216](https://github.com/babashka/cli/issues/216): in a cluster of flags, where no letter takes a value, an interior hyphen is an error instead of silently ending option parsing. 
        
           - Fix: a value bound with `--foo=val` may start with a hyphen: `--foo=-bar` binds `"-bar"` instead of reporting a missing value 
        
           ## 0.12.87 
        
           - `dispatch`: the command named on the command line wins over the `:exec-args` of its ancestors. A value the user typed at an ancestor level still wins over both 
        
           - Completion: the fish snippet registers with `--keep-order`, so fish offers options in the order they are emitted, long option before its short alias, rather than sorting short options first 
        
           ## 0.12.86 
        
           - Help: show the dispatch-level `:spec` options under `Inherited options:`. The parser always accepted these options, but help did not show them 
        
           - Help: `format-command-help` accepts `:spec`, the dispatch-level spec, so a standalone call shows the same options as `dispatch` 
        
           - Completion: do not offer `:positional` keys as options, they are rejected when typed as a flag 
        
           ## 0.12.85 
        
           - Help: separate command names and docs with two spaces, like the `Options:` and `Arguments:` sections 
        
           ## 0.12.84 
        
           - zsh completion: offer a command's options without typing a dash first, by opting the registered program names out of zsh's `prefix-needed` style 
        
           ## 0.12.83 
        
           - Populate `:msg` in the `:error-fn` data for `dispatch` command errors (`:no-match`, `:input-exhausted`), like option errors already carry it 
        
           - zsh completion: classify an option without a `:desc` as an option. It was added as a value, which offered it where zsh hides described options 
        
           ## 0.12.81 
        
           - Fix: a required `:inherit` option is no longer reported missing when supplied after its command 
        
           ## 0.12.80 
        
           - Add ordered `:enum` values for validation, help and completion 
        
           - Show sorted set-valued `:validate` values in `--help` 
        
           - Show `:args->opts` entries under `Arguments:` in `--help` 
        
           - Validate repeatable option values individually 
        
           - Support `:doc` and `:epilog` as a vector of lines, joined with newlines 
        
           ## v0.12.79 
        
           - Verify that `:cmd` is a string, keyword or symbol

They do have tags right?

Yep!

Folks do sometimes look at GitHub Releases though.
And they sometimes Watch a GitHub repo for new Releases.

@lread

@lread Not all projects use releases, e.g. tools.deps doesn't either I think, but...

you can follow releases using an Atom/RSS reader:

https://github.com/babashka/cli/tags.atom

Yes, only trying to be helpful, not trying to tell you what you should do here. 🙂

I noticed this project already has GitHub Releases.
I saw that these were no longer being created.
I thought maybe there was some automation/process that was broken unintentionally.

Clojure tools.deps has never had Releases, so nothing seems broken there.

I was just too lazy to make those Githubt releases after I scripted bb publish --bump locally :)

(= lazy borkdude)
=> false

Feel free to close this issue if you don't care about this kind of thing.
For me, I do feel it will be confusing for some people coming to this GitHub repo.

Navigation Menu

Repository navigation

Missing some GitHub Releases #234

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	## 0.12.91

	- zsh completion: disable sorting for registered program names to preserve candidate order

	## 0.12.90

	- `dispatch`: add `:supplied` to the opts map's `:org.babashka/cli` metadata with the set of option keys given on the command line

	## 0.12.89

	- [#244](https://github.com/babashka/cli/issues/244): use metadata and docstrings from `:fn` and `:exec-fn` vars in babashka and ClojureDart

	## 0.12.88

	- [#219](https://github.com/babashka/cli/issues/219): `:cmd-aliases` on a table entry or tree node gives a command one or more alternative names.
	- A short option that declares a non-boolean `:coerce` takes the rest of its token as its value, like getopt: `-J-Dfoo=bar` binds `"-Dfoo=bar"`, `-p80` binds `80`. One leading `=` is stripped, like `--foo=bar`. Flag letters may precede the valued option in a cluster: with `:b` a flag and `:a` valued, `-ba x` parses as `-b -a x`
	- [#216](https://github.com/babashka/cli/issues/216): in a cluster of flags, where no letter takes a value, an interior hyphen is an error instead of silently ending option parsing.
	- Fix: a value bound with `--foo=val` may start with a hyphen: `--foo=-bar` binds `"-bar"` instead of reporting a missing value

	## 0.12.87

	- `dispatch`: the command named on the command line wins over the `:exec-args` of its ancestors. A value the user typed at an ancestor level still wins over both
	- Completion: the fish snippet registers with `--keep-order`, so fish offers options in the order they are emitted, long option before its short alias, rather than sorting short options first

	## 0.12.86

	- Help: show the dispatch-level `:spec` options under `Inherited options:`. The parser always accepted these options, but help did not show them
	- Help: `format-command-help` accepts `:spec`, the dispatch-level spec, so a standalone call shows the same options as `dispatch`
	- Completion: do not offer `:positional` keys as options, they are rejected when typed as a flag

	## 0.12.85

	- Help: separate command names and docs with two spaces, like the `Options:` and `Arguments:` sections

	## 0.12.84

	- zsh completion: offer a command's options without typing a dash first, by opting the registered program names out of zsh's `prefix-needed` style

	## 0.12.83

	- Populate `:msg` in the `:error-fn` data for `dispatch` command errors (`:no-match`, `:input-exhausted`), like option errors already carry it
	- zsh completion: classify an option without a `:desc` as an option. It was added as a value, which offered it where zsh hides described options

	## 0.12.81

	- Fix: a required `:inherit` option is no longer reported missing when supplied after its command

	## 0.12.80

	- Add ordered `:enum` values for validation, help and completion
	- Show sorted set-valued `:validate` values in `--help`
	- Show `:args->opts` entries under `Arguments:` in `--help`
	- Validate repeatable option values individually
	- Support `:doc` and `:epilog` as a vector of lines, joined with newlines

	## v0.12.79

	- Verify that `:cmd` is a string, keyword or symbol

Missing some GitHub Releases #234

Description

Activity

borkdude commented on Sep 24, 2026

lread commented on Sep 24, 2026

lread commented on Sep 24, 2026

borkdude commented on Sep 25, 2026

lread commented on Sep 25, 2026

borkdude commented on Sep 25, 2026

lread commented on Sep 25, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions