v0.1.5

Added

• The stamped .clj-kondo/config.edn reads resources/clj-kondo.exports/io.github.af2b/<repository>/, where a library that has
  macros ships the configuration and the hooks that teach clj-kondo about them: its own lint reads it, and the projects that depend on
  it import it. A repository without one is not affected.

v0.1.4

Fixed

• --services '[postgres]' was ignored: bb -x hands the stamp a string, not a vector, and the services of a project came out
  as none, so the pipeline of a library with integration tests quietly left them out. The stamp reads "[postgres redis]" and
  "postgres,redis" as well as a collection, and refuses a service that the pipelines cannot start, naming it.

v0.1.3

Fixed

• The release adopts the release that already exists for the tag, draft or not, uploads the assets over it and publishes it, and
  retries up to five times with a growing pause. The GitHub API answered a 5xx while creating a release, which left an empty
  draft behind, and a re-run of the job then failed on the draft.

v0.1.2

Fixed

• Every job resolves the dependencies in a step of its own, retried three times with a growing pause: Maven Central rate-limits
  shared runner addresses now and then, and the first release of a library failed on an HTTP 403 that a re-run did not repeat.
• make deps warms every alias on its own and the Babashka classpath; a single combined classpath did not.
• The release notes print the coordinate in the shape the README uses, ready to paste into deps.edn.

v0.1.1

Fixed

• The reflection check ran the Clojure CLI with the aliases' :main-opts, so in a repository whose :test alias starts a
  test runner the program never ran. It now loads the namespaces from the classpath.
• The audit target passes the bill of materials to osv-scanner with -L, the replacement of the deprecated --sbom.

Changed

• The formatter indents the body of a property test (for-all) like the body of a let.

v0.1.0

First release.

Added

• Reusable GitHub workflows for a Clojure library: the quality gate, the release and the weekly scheduled checks.
• Babashka tasks: a CycloneDX bill of materials, a reflection check, a conventions check (documentation per parameter,
  arglist layout, line length), release checks and notes, and the stamping of the standard into a repository.
• Templates of the files every repository follows: license, security policy, contributing guide, code of conduct, issue and
  pull request templates, editor, formatter and lint configuration, Makefile, build.clj and the caller workflows.
• The standard and the decisions behind it.