Closed jankatins closed 2 years ago
The worklow apparently needs your approval (and a new tag anyways, before running) :-)
thanks for doing all this work. i'll push a new tag (there's been a minor functionality change since 0.6.6 that hasn't had a tagged release yet) to kick the tires
My pleasure, this was easier than maintaining my rust apps update script :-)
@tummychow There seems to be an easy way to generate the changelog based on the commits: https://github.com/alist-org/alist/commit/eb15bce24b2bceff0a81696b38ac85cca575adde -> uses https://github.com/Bullrich/generate-release-changelog
Want to get an PR adding that?
hm, i'd want to filter it to only commits touching relevant files (rust code, cargo.toml/lock, manpages), we've had plenty of commits on project infra lately that wouldn't belong in a changelog. looks like the action script doesn't have an option for that. i'd accept a pr that vendors the action into this repo's .github
plus adding that filter, or if you can find another fork that supports filtering you could use that one instead
Example run and corresponding release:
This is based on a master push with a example tag. I had some problems making it work in branch but this should be more or less the same as a regular release.
Workflow after merging this:
Currently, the binaries are in a archive (together with some doc stuff), so any install script needs to be adjusted to untar/unzip and get the binary from a versioned subdir (zinit can do that, so I'm happy) instead of renaming/linking to the versioned binary.
Example extract:
Closes: #39 #59
Tested on linux and mac by running
git-absorb --help