Changelog¶
Generated from this repository’s tags by the extension on the previous page. Nothing below is committed anywhere: an entry’s release is worked out from the tag trees on every build.
Unreleased¶
Added
cli: The nix package installs bash completions for
moneta.
Changed
Breaking: cli: The nix git hooks are a wrk module,
wrkModules.default, in place ofdevShells.<system>.git-hooks. Import it in your flake’swrkoutput and setmoneta.enable = true. Entering the checkout withwrkputsmonetaonPATHand registers the same three hooks, in a git config file that wrk keeps from being garbage-collected, so a hook no longer breaks afternix-collect-garbage.moneta.packageandmoneta.commandpick themonetaonPATHand the one the hooks run.
v0.3.6 — 2026-10-22¶
Added
cli, go-api: A fragment can name the release it shipped in with
released_in:(andmoneta new --released-in), so a changelog imported from another tool keeps its old releases instead of crediting every entry to the next one. The tag has to exist, whichmoneta checkverifies; with modules it takes one tag per module, andrender --format jsonmarks such an entry"pinned": true. Go programs set it withFragmentSpec.ReleasedIn.
v0.3.5 — 2026-10-22¶
Added
cli: moneta release can pack the builds of one OS in a format of their own, such as a zip for Windows beside tar.xz everywhere else: set
archive.format-overrides, a map fromGOOSto format. An override for an OS that no build is for is an error whenomniblack.yamlloads.cli, go-api: moneta release can sign each binary on its own, for a program that verifies the file it unpacked rather than the checksums, such as a self-updater. Give the build a
signaturename template, such as{{ .File }}_{{ .Os }}_{{ .Arch }}.sig:.Fileis the binary with.exeon Windows, and is also available inarchive.name. The signatures are listed in the checksums and uploaded with the release, and a snapshot makes none. Go programs find them inReleaseResult.Signatures.cli: moneta release can publish an archive of one directory beside the source archive, such as a website a binary downloads and builds from: list it under
moneta.release.extra-sourceswith apathand aname. The archive holds the tracked files of the directory at the released commit, relative to it, underprefix(""for the root), with anyfilesbeside them, andsign: truepublishes a signature of it. A missing directory is refused before anything is tagged.
v0.3.4 — 2026-10-21¶
Added
cli: moneta release can keep a Modrinth project’s description up to date. Name a build in
moneta.release.modrinth.body-from, and on every release moneta sets the description to the file that build writes, as it is, before it creates the version. The file is published under its own name and listed in the checksums, and is not uploaded as a file of the version.--publish-onlysets it again, and--dry-runshows what it would send.
v0.3.3 — 2026-10-21¶
Added
cli: moneta release can build once for every platform, for a jar or a script: set a build’s
platformsto[any]. The mage target runs once withGOOSandGOARCHempty, and the defaultarchive.nameleaves the platform out, giving for examplemod.jar_1.2.3.tar.gz. The default name is unchanged for builds with a platform.cli: moneta release can publish a build’s binary without an archive: set
archive.format: none. The binary is listed and signed in the checksums like an archive, and checked against them on a resume or--publish-only.archive.namerenames it, for examplemod_{{ .Version }}.jar, so the mage target can keep writing one fixed name. Go programs find these files in the newReleaseResult.Binaries.cli, go-api: moneta release can publish each release to Modrinth as well, so a Minecraft mod needs no second upload step in Gradle. Set
moneta.release.modrinthwith the project, a token file and the loaders. The game versions can be read from a key ofgradle.propertiesat the released commit, withgame-versions-from. The version number, the changelog and the version type (release, beta or alpha) come from the release itself. A version on Modrinth is never replaced:releaseand--publish-onlyleave one that exists alone, and a release that reached GitLab but not Modrinth is finished by runningreleaseagain. Go programs find the new version inReleaseResult.Modrinth.
v0.3.2 — 2026-09-26¶
Added
cli: moneta release can announce a release on Discord. Set
moneta.release.announce.discord.webhook-fileto a file that holds a webhook URL, and each published release is posted to that channel as an embed with amessagetemplate, then the release notes, linked to the release page;usernameandavatar-urlset the name and picture it is posted under. If the post fails, the release stays published andmoneta release --announce-onlyposts it.--publish-onlynever announces, and--dry-runshows the message without posting it.
v0.3.1 — 2026-09-26¶
Added
cli, go-api: Cut a release with
moneta release, and build one without publishing it withmoneta snapshot. moneta tags the versionmoneta nextsuggests, builds each platform through your own mage target, packs and checksums the binaries, signs them withsq, pushes the tag and publishes a GitLab release with the notes. Configure it underrelease:inmoneta:, and in each module’smoneta:. A magefile reads what to build from the newgitlab.com/terryp/moneta/buildenvpackage, and a Go program runs a release withRepo.Release. This was capyreleaser: move itscapyreleaser:blocks undermoneta:asrelease:, and readMONETA_BUILD_*where the magefile readCAPY_*.capyreleaser checkismoneta release --plan.cli: Every template in
omniblack.yamlcan calllower,upperandtitle.
v0.3.0 — 2026-09-26¶
Changed
Breaking: cli, go-api:
modulesmoved from undermoneta:to a top-level list in omniblack.yaml, since the other omniblack tools release by the same modules. Each entry keepsname,path,tag-prefixandtag-pattern, and takesfirst-version,sinceandreleasesunder its ownmoneta:. moneta stops with an error that says wheremoneta.moduleswent. A key in a module entry that is neither a module setting nor a known tool’s block is a warning, and Go programs get it asConfig.Warnings. An older moneta does not see the new list and renders one changelog for the whole repository, so upgrade moneta in the same change that moves it.
v0.2.2 — 2026-09-26¶
Added
cli, go-api:
moneta next --tag --signcreates a signed tag, with the key and format git is configured with, and fails rather than create it unsigned when the key is missing or locked:tag.gpgsignsigns only on a machine whose config sets it. In Go this isTagOptions.Sign; combined withLightweight,TagreturnsErrSignLightweight.
v0.2.1 — 2026-09-26¶
Added
go-api: A Go program can now read a changelog without running the binary:
import "gitlab.com/terryp/moneta", thenmoneta.Open,Repo.Changelog(orRepo.ChangelogAtfor the module that holds a directory), andChangelog.Document,RenderorVersions, which return whatmoneta renderandmoneta listprint. Errors a caller can check witherrors.Isanderrors.AsincludeErrShallow,ErrModuleRequired,ErrNoHeadTag,*UnknownVersionErrorand*ConfigError. The API is v0 and can still change.go-api: A Go program can now work out and cut the next release without running the binary:
Changelog.Nextreturns whatmoneta nextprints as aSuggestion(version, bump, the release it moves from, and the commit it is for), andChangelog.Tagcreates that tag and can push it.Tagrefuses a commit that already has a release tag (ErrHeadTagged) or a suggestion with nothing pending (ErrNothingPending) unlessTagOptions.Forceis set, and a failed push returns a*PushError, since the tag was already created.go-api: A Go program can now run
moneta checkwithout the binary:Repo.Checkreturns aCheckReportthat lists each broken fragment with its path, each commit whose message names an unknown scope, and whether the branch owes a fragment, so a finding is data and not an error string. The error is kept for a check that could not run, such asErrNoBasewhen nothing names a base.CheckReport.Errgives the text the command prints, and a branch that owes a fragment matchesErrFragmentOwed.ParseCommitMessage,Repo.CheckCommitMessageandRepo.StripCommitMessagearemoneta commit-msg.CheckOptionstakes the merge-request base and the default branch that the command reads fromCI_MERGE_REQUEST_DIFF_BASE_SHAandCI_DEFAULT_BRANCH, because the library reads no environment.go-api: A Go program can now write a change fragment without the binary.
Repo.ComposeFragmentworks out a fragment from aFragmentSpec– its path, itsid:and its content – and writes nothing, which ismoneta new --dry-run.Repo.WriteFragmentputs it in the changes directory; it refuses onemoneta checkwould reject, returnsErrEmptyFragmentfor one with no entry text, and never overwrites a file, which matchesfs.ErrExist.Repo.ReviseFragmenttakes the content back from an editor and names the file again from what it now says, keeping the time and id it was composed with.FragmentSpec.Atfixes the time the filename and the id carry.Repo.AddsFragmentandRepo.IsInternalanswer whatmoneta commitasks before it offers a fragment, andCommitMessage.Stringwrites a message back out as a subject line.docs, go-api: The site has a page on the Go API, which maps each command to its method and lists the errors a caller can branch on. On pkg.go.dev, runnable examples show a release (
Next,Tag, then the notes of the new tag) andRepo.Check. The documentation ofSuggestion.Bumpnow says that below 1.0 it is the bump the entries ask for, not how far the version moved.
Changed
cli: The command moved to
cmd/moneta, sogo install gitlab.com/terryp/moneta/cmd/moneta@latestinstalls it.go install gitlab.com/terryp/moneta@latestno longer works.cli:
moneta checknow reports every problem in one run. A broken fragment no longer hides a commit with an unknown scope, and neither hides a branch that owes a fragment. Before, the check stopped at the first kind of problem, so a pipeline could fail three times for three different reasons.
Fixed
cli: In a repository with modules,
render --sinceand--untilnow read a tag under the module’s prefix, such ascore/v0.1.0. Before,--sincekept that release and--untildropped it.cli:
render -o FILEno longer emptiesFILEwhen the render fails, such as a--bodyselection that holds two versions or a template that fails to run. The file is written only after the whole changelog renders.cli:
moneta newnow refuses a fragment thatmoneta checkwould reject: an internal scope, a scope not in the list whenstrict-scopesis on, or no issue whenissues.requiredis set. Before, it wrote the file, and the pipeline failed on it later.--dry-runrefuses it too.
v0.2.0 — 2026-09-25¶
Added
Install moneta and the Sphinx extension from another nix flake.
overlays.defaultaddsmonetato the package set andmoneta-sphinxto every python version’s, so a site pinned to an older interpreter takes it the same way.cli: Check commit messages with
moneta commit-msg, for a git hook, and withmoneta check --commits, for every commit on a branch. A subject isscope: Subject,a,b: SubjectorSubject, and every scope must be in thescopeslist ofomniblack.yaml.moneta check --require-fragmentnow passes a branch that adds no fragment when every commit on it is in an internal scope.cli: A nix dev shell,
devShells.<system>.git-hooks, forinputsFromin your own dev shell. Entering the shell putsmonetaonPATHand sets git hooks in the repository:commit-msgchecks the scopes of the commit message,pre-commitrunsmoneta check, andpre-pushrunsmoneta check --commits --require-fragmenton each ref being pushed. The hooks are config-based (hook.<name>.event), so they run beside the hooks the repository already has.cli:
moneta checktakes a ref:moneta check featurechecks that commit rather than the checkout. It lints the fragments in its tree, and--commitsand--require-fragmentcheck the commits and changes from the base to it. The working tree is not read.cli:
moneta render --bodyrenders one release without its version heading, for a release page that shows the version in its title already. The Markdown kind headings move up to##. It fails unless the selection holds exactly one version, so the notes cannot include a second release by accident.cli:
moneta commitstarts a commit from a form. You pick the scopes from thescopeslist and type the subject, and it opensgit commitwithscope: Subjectalready in the editor. If no internal scope is picked, it offers to write a change fragment and stages the fragment into the same commit. The offer defaults to no when the branch already adds a fragment. Arguments after--go togit commit.cli, docs-ext: A repository can now keep a changelog for each module. Declare the modules in
moneta.modules, and name the modules of each fragment inmodules:. Each module has its own tags, such ascore/v1.2.0, and its own releases.render,nextandlisttake--module(-M), or find the module from$MONETA_MODULEor from the directory they run in. The Sphinx extension takes:module:on the directive andmoneta_moduleinconf.py. The JSON has amodulefield on the document and amodulesfield on each entry.cli, docs-ext: Take an entry out of the changelog with
retracted: truein its frontmatter, released versions included. Deleting a fragment does not remove its entry, because a revert deletes it too.cli, docs: Write an
id:into every fragmentmoneta new,createandcommitmake, so moving or renaming one keeps its entry.moneta.idsets the template, a UUIDv7 by default, andid: ""turns it off. In the release where this starts, entries that have an id sort ahead of older entries of the same kind.
Changed
Breaking: Read the configuration from
omniblack.yaml, a file shared with the other omniblack tools, instead of.moneta.yaml. Move moneta’s settings under amoneta:key.scopesis now a top-level list, notscopes.known, andscopes.strictis nowmoneta.strict-scopes. moneta ignores top-level keys that belong to other tools. If.moneta.yamlis still the nearest configuration file, moneta stops with an error. It does not fall back to the defaults.Breaking: cli: Write each entry of the
scopeslist inomniblack.yamlas a mapping:- name: parser, withinternal: truefor a part of the project that users cannot see. A plain string is now an error. A fragment cannot use an internal scope, andmoneta createdoes not offer one.cli: moneta now counts a tag as a release only when it is a version under
tag-prefix. Before, every tag was a release, so a tag such aslatestordeploy-2026showed in the changelog and took the entries of the release after it. To choose the release tags yourself, settag-patternto a glob, for example"a/v*"in a repository that releases more than one component.cli: An
id:added, changed or removed after a release no longer duplicates the entry: moneta follows the key, andmoneta checkno longer fails on it. A fragment with anid:keeps its entry through a rename. A deleted fragment now renders from its last version in the history, with the corrections made to it, not from the copy in its tag.cli, docs: Name a new fragment after its description and then the UTC date and time, as in
add-a-thing-2026-09-25-14-30.md, instead of starting with a timestamp.moneta.filenamecan use the new{{ .Year }},{{ .Month }},{{ .Day }},{{ .Hour }}and{{ .Minute }}fields. Existing fragments keep their names.
Fixed
cli:
check.require-fragmentinomniblack.yamlnow does something:moneta checkasks for a fragment without the flag, and--require-fragment=falseturns the gate off for one run. It is off by default, so a plainmoneta checkin a repository with no config only validates the fragments. The pre-commit hook of thegit-hooksdev shell passes--require-fragment=false, since the fragment can be in any commit on the branch.cli: Pushing a release tag now checks what the release adds.
moneta check <tag>compares a release tag with the latest release in its history, not with the default branch, which already holds the tagged commit and so passed the tag having checked nothing. Thepre-pushhook of thegit-hooksdev shell gives tags tocheckby name for this.
v0.1.0 — 2026-09-24¶
Added
Attribute change fragments to the first tag whose tree contains them
Read entry text live, so a typo fixed after release reaches the render
Refuse to run in a shallow clone, where ancestry answers wrongly
Render the changelog as Markdown, reStructuredText or JSON
Suggest the next version from the kinds of change waiting to be released
Fail check when a fragment key changed after release and the entry appears twice
Mark a release yanked with a yanked/ tag, so its entries ship again in the next release
Write a change fragment interactively with moneta create
Render the changelog into a Sphinx site with the moneta_sphinx extension
Link each release heading to a URL built from
releases.url, a Go template over the tag.
Changed
Take several scopes on one fragment, and rename the JSON field to scopes
Breaking: Spell every
.moneta.yamltemplate as a Go text/template:issues.urlandmerge-requests.urltake{{ .ID }}rather than{id}, andfilenametakes{{ .Timestamp }},{{ .Kind }},{{ .Scope }}and{{ .Slug }}. A misspelled field is now an error at load instead of text left in the output.