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 of devShells.<system>.git-hooks. Import it in your flake’s wrk output and set moneta.enable = true. Entering the checkout with wrk puts moneta on PATH and registers the same three hooks, in a git config file that wrk keeps from being garbage-collected, so a hook no longer breaks after nix-collect-garbage. moneta.package and moneta.command pick the moneta on PATH and 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: (and moneta 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, which moneta check verifies; with modules it takes one tag per module, and render --format json marks such an entry "pinned": true. Go programs set it with FragmentSpec.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 from GOOS to format. An override for an OS that no build is for is an error when omniblack.yaml loads.

  • 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 signature name template, such as {{ .File }}_{{ .Os }}_{{ .Arch }}.sig: .File is the binary with .exe on Windows, and is also available in archive.name. The signatures are listed in the checksums and uploaded with the release, and a snapshot makes none. Go programs find them in ReleaseResult.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-sources with a path and a name. The archive holds the tracked files of the directory at the released commit, relative to it, under prefix ("" for the root), with any files beside them, and sign: true publishes 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-only sets it again, and --dry-run shows 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 platforms to [any]. The mage target runs once with GOOS and GOARCH empty, and the default archive.name leaves the platform out, giving for example mod.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.name renames it, for example mod_{{ .Version }}.jar, so the mage target can keep writing one fixed name. Go programs find these files in the new ReleaseResult.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.modrinth with the project, a token file and the loaders. The game versions can be read from a key of gradle.properties at the released commit, with game-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: release and --publish-only leave one that exists alone, and a release that reached GitLab but not Modrinth is finished by running release again. Go programs find the new version in ReleaseResult.Modrinth.

v0.3.2 — 2026-09-26

Added

  • cli: moneta release can announce a release on Discord. Set moneta.release.announce.discord.webhook-file to a file that holds a webhook URL, and each published release is posted to that channel as an embed with a message template, then the release notes, linked to the release page; username and avatar-url set the name and picture it is posted under. If the post fails, the release stays published and moneta release --announce-only posts it. --publish-only never announces, and --dry-run shows 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 with moneta snapshot. moneta tags the version moneta next suggests, builds each platform through your own mage target, packs and checksums the binaries, signs them with sq, pushes the tag and publishes a GitLab release with the notes. Configure it under release: in moneta:, and in each module’s moneta:. A magefile reads what to build from the new gitlab.com/terryp/moneta/buildenv package, and a Go program runs a release with Repo.Release. This was capyreleaser: move its capyreleaser: blocks under moneta: as release:, and read MONETA_BUILD_* where the magefile read CAPY_*. capyreleaser check is moneta release --plan.

  • cli: Every template in omniblack.yaml can call lower, upper and title.

v0.3.0 — 2026-09-26

Changed

  • Breaking: cli, go-api: modules moved from under moneta: to a top-level list in omniblack.yaml, since the other omniblack tools release by the same modules. Each entry keeps name, path, tag-prefix and tag-pattern, and takes first-version, since and releases under its own moneta:. moneta stops with an error that says where moneta.modules went. 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 as Config.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 --sign creates 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.gpgsign signs only on a machine whose config sets it. In Go this is TagOptions.Sign; combined with Lightweight, Tag returns ErrSignLightweight.

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", then moneta.Open, Repo.Changelog (or Repo.ChangelogAt for the module that holds a directory), and Changelog.Document, Render or Versions, which return what moneta render and moneta list print. Errors a caller can check with errors.Is and errors.As include ErrShallow, ErrModuleRequired, ErrNoHeadTag, *UnknownVersionError and *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.Next returns what moneta next prints as a Suggestion (version, bump, the release it moves from, and the commit it is for), and Changelog.Tag creates that tag and can push it. Tag refuses a commit that already has a release tag (ErrHeadTagged) or a suggestion with nothing pending (ErrNothingPending) unless TagOptions.Force is set, and a failed push returns a *PushError, since the tag was already created.

  • go-api: A Go program can now run moneta check without the binary: Repo.Check returns a CheckReport that 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 as ErrNoBase when nothing names a base. CheckReport.Err gives the text the command prints, and a branch that owes a fragment matches ErrFragmentOwed. ParseCommitMessage, Repo.CheckCommitMessage and Repo.StripCommitMessage are moneta commit-msg. CheckOptions takes the merge-request base and the default branch that the command reads from CI_MERGE_REQUEST_DIFF_BASE_SHA and CI_DEFAULT_BRANCH, because the library reads no environment.

  • go-api: A Go program can now write a change fragment without the binary. Repo.ComposeFragment works out a fragment from a FragmentSpec – its path, its id: and its content – and writes nothing, which is moneta new --dry-run. Repo.WriteFragment puts it in the changes directory; it refuses one moneta check would reject, returns ErrEmptyFragment for one with no entry text, and never overwrites a file, which matches fs.ErrExist. Repo.ReviseFragment takes 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.At fixes the time the filename and the id carry. Repo.AddsFragment and Repo.IsInternal answer what moneta commit asks before it offers a fragment, and CommitMessage.String writes 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) and Repo.Check. The documentation of Suggestion.Bump now 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, so go install gitlab.com/terryp/moneta/cmd/moneta@latest installs it. go install gitlab.com/terryp/moneta@latest no longer works.

  • cli: moneta check now 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 --since and --until now read a tag under the module’s prefix, such as core/v0.1.0. Before, --since kept that release and --until dropped it.

  • cli: render -o FILE no longer empties FILE when the render fails, such as a --body selection that holds two versions or a template that fails to run. The file is written only after the whole changelog renders.

  • cli: moneta new now refuses a fragment that moneta check would reject: an internal scope, a scope not in the list when strict-scopes is on, or no issue when issues.required is set. Before, it wrote the file, and the pipeline failed on it later. --dry-run refuses it too.

v0.2.0 — 2026-09-25

Added

  • Install moneta and the Sphinx extension from another nix flake. overlays.default adds moneta to the package set and moneta-sphinx to 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 with moneta check --commits, for every commit on a branch. A subject is scope: Subject, a,b: Subject or Subject, and every scope must be in the scopes list of omniblack.yaml. moneta check --require-fragment now 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, for inputsFrom in your own dev shell. Entering the shell puts moneta on PATH and sets git hooks in the repository: commit-msg checks the scopes of the commit message, pre-commit runs moneta check, and pre-push runs moneta check --commits --require-fragment on each ref being pushed. The hooks are config-based (hook.<name>.event), so they run beside the hooks the repository already has.

  • cli: moneta check takes a ref: moneta check feature checks that commit rather than the checkout. It lints the fragments in its tree, and --commits and --require-fragment check the commits and changes from the base to it. The working tree is not read.

  • cli: moneta render --body renders 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 commit starts a commit from a form. You pick the scopes from the scopes list and type the subject, and it opens git commit with scope: Subject already 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 to git 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 in modules:. Each module has its own tags, such as core/v1.2.0, and its own releases. render, next and list take --module (-M), or find the module from $MONETA_MODULE or from the directory they run in. The Sphinx extension takes :module: on the directive and moneta_module in conf.py. The JSON has a module field on the document and a modules field on each entry.

  • cli, docs-ext: Take an entry out of the changelog with retracted: true in 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 fragment moneta new, create and commit make, so moving or renaming one keeps its entry. moneta.id sets the template, a UUIDv7 by default, and id: "" 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 a moneta: key. scopes is now a top-level list, not scopes.known, and scopes.strict is now moneta.strict-scopes. moneta ignores top-level keys that belong to other tools. If .moneta.yaml is 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 scopes list in omniblack.yaml as a mapping: - name: parser, with internal: true for a part of the project that users cannot see. A plain string is now an error. A fragment cannot use an internal scope, and moneta create does 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 as latest or deploy-2026 showed in the changelog and took the entries of the release after it. To choose the release tags yourself, set tag-pattern to 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, and moneta check no longer fails on it. A fragment with an id: 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.filename can use the new {{ .Year }}, {{ .Month }}, {{ .Day }}, {{ .Hour }} and {{ .Minute }} fields. Existing fragments keep their names.

Fixed

  • cli: check.require-fragment in omniblack.yaml now does something: moneta check asks for a fragment without the flag, and --require-fragment=false turns the gate off for one run. It is off by default, so a plain moneta check in a repository with no config only validates the fragments. The pre-commit hook of the git-hooks dev 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. The pre-push hook of the git-hooks dev shell gives tags to check by 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.yaml template as a Go text/template: issues.url and merge-requests.url take {{ .ID }} rather than {id}, and filename takes {{ .Timestamp }}, {{ .Kind }}, {{ .Scope }} and {{ .Slug }}. A misspelled field is now an error at load instead of text left in the output.