Something went wrong. Try again.
vibescrobble! every agent, live on stage. vibescrobble.com
atproto agent llm did
Something went wrong. Try again.
vibescrobble.com release.toml
2.6 kB · 51 lines
TOML
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152# cargo-release (https://github.com/crate-ci/cargo-release). git-cliff decides# what the next version is (cliff.toml); this decides what happens to the tree# when it is applied. Run from `main`, by a person — never from a feature# branch, and never inside a pull request.## Everything that leaves the machine is off. This publishes nothing:# no crates.io release and no artifacts; the CLI's binaries are published by# scripts/release.sh when the tag this makes is deployed. What is wanted is# narrow — the workspace version moves, Cargo.lock follows it, and a tag marks# where the next bump starts counting from.
# Not `cargo publish`, not now and not by accident. Every crate also carries# publish = false in its manifest, so this is the second of two locks.publish = false
# No `git push`. The bump is a local act, reviewed like any other commit before# it goes anywhere, and pushing a tag is deliberately a separate command.push = false
# One version across every crate in the workspace. These crates are one product# released together, not independently useful libraries, and a reader who sees# vibescrobble-index 0.4.2 next to vibescrobble-query 0.1.9 has learned nothing# except that the numbers are meaningless. It is also what makes a single tag# and a single README line correct below.shared-version = true
# One commit for the whole bump rather than one per crate. With shared-version# set, {{version}} still renders in the message; without it, cargo-release# leaves the placeholder as literal text.consolidate-commits = true
# The version commit has to satisfy the commit-msg hook (prek.toml), because# cargo-release shells out to `git commit` and the hook fires. Hence the# `chore(release):` prefix and the lower-case description; `chore` is in# committed.toml's allowed_types for exactly this.pre-release-commit-message = "chore(release): vibescrobble v{{version}}"
# A tag is the one piece that is not optional. `git cliff --bumped-version`# counts commits since the most recent tag, so a bump that leaves no tag cannot# be run twice: the second run would recompute from the same starting point and# hand back the same answer.## The name carries no crate name, which is what keeps a workspace bump to a# single tag rather than one per member.tag = truetag-name = "v{{version}}"
# `tag-message` being set is what makes the tag annotated rather than# lightweight, and that distinction reaches past git's own rules: an annotated# tag is an object with its own hash, and Tangled keys off that object.tag-message = "vibescrobble {{tag_name}}"