Home › Docs › Workflow guides

Version configuration revisions

Immutable history
Workflow

Version configuration revisions

Create amendments instead of overwriting mutable state, then use lineage and diff views to review what changed.

When to use it

Use this when

  • A config snippet changes over time and reviewers need each revision preserved.
  • You want stable links to historical versions plus a latest link for the chain.
Steps

Do this

  1. Create the first version Publish the baseline as an unlisted or profile paste with a syntax hint such as yaml, toml, or json.
  2. Amend with context Create a child version using parent_id or the web edit form. Add a short change_note when automation calls the API or MCP.
  3. Review the chain Use the lineage endpoint, /chain page, /latest, or /diff to inspect visible versions.
Examples

Copyable commands

CLI amendment
pbca new --file config.v1.yaml --syntax yaml --title "staging config"
pbca new --file config.v2.yaml --syntax yaml --parent 2EREFnGBXq
REST lineage
curl -sS https://pastebin.ca/api/v1/lineage/2EREFnGBXq
open https://pastebin.ca/2EREFnGBXq/diff
Operational notes

Keep in mind

  • Amendments create new paste IDs. Existing URLs keep pointing at the exact version they originally referenced.
  • MCP amend_paste supports plaintext, public-access parent versions; encrypted amendments are intentionally not available over MCP.