changesets

pleme-io · changesets

Run npm/changesets version + publish flow.

Category: release-mgmt — 📦 Release management — Changesets / semantic-release Backend: tatara-lisp Auto-published: pinnable via @v0.13.x tags or floating @v1 / @main

30-second quickstart

steps:
  - uses: actions/checkout@v4
  - uses: pleme-io/actions/changesets@v1
    with:
      publish: "true"

Inputs

Name	Required	Default	Description
publish	no	true

Outputs

Name	Description
published-count

Configuration via .pleme-io-release.toml

Per-repo defaults follow 3-tier precedence: env var (workflow input) > .pleme-io-release.toml > hardcoded default.

See the full config schema.

Architecture

Composite GitHub Action. Logic lives in run.tlisp; action.yml orchestrates install steps + one tatara-script invocation.

Per the ★★ NO-SHELL prime directive (pleme-io-pattern-core skill): this action's primary logic is typed Lisp, not bash. The substrate's action-shell-lint enforces this fleet-wide on every PR.

Related primitives — release-mgmt category

release-please · release-promote · semantic-release · yank-version

Auto-published on free public CI

Every push to main on pleme-io/actions:

1. auto-bump.yml fires (~10s) → tags v0.13.{next}
2. release.yml cuts the Docker image (if applicable) + fast-forwards v1
3. Consumers using @v1 see the new revision automatically

$0/month cost — GitHub-hosted runners + public-repo free tier.

License

MIT.

---

Auto-generated from action.yml by pleme-doc-gen. Do not hand-edit.