Skip to content

docs: adopt scriv changelogs across the ecosystem (ADR 0009)#6

Merged
Unisay merged 1 commit into
masterfrom
issue-101/changelog-canon
Jun 25, 2026
Merged

docs: adopt scriv changelogs across the ecosystem (ADR 0009)#6
Unisay merged 1 commit into
masterfrom
issue-101/changelog-canon

Conversation

@Unisay

@Unisay Unisay commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

docs: adopt scriv changelogs across the ecosystem (ADR 0009)

The pre-release FFI campaign (purescript#73-purescript#102) flipped the tradeoff that ADR 0006 made: the fork tags carry one line each, and the only place those lines are aggregated is this repo's set-bump commit messages. A consumer pinning numbers v9.1.3 has no way to read what moved since v9.1.0 without walking two git logs. So the whole ecosystem moves to a managed changelog.

What

  • ADR 0009 records the decision: every repo keeps a CHANGELOG.md managed with scriv. It supersedes only the no-changelog clause of ADR 0006; the rest of the tag-driven release flow stands. ADR 0006's status notes the supersession and the index lists 0009.
  • CONTRIBUTING gains a Changelogs section (a fragment per src/ change) and a scriv collect --version <tag> step at the front of the release flow.
  • This repo gets its own scriv-managed CHANGELOG.md, backfilled with the psc-* set releases (the FFI campaign window and the new-spago migration), plus changelog.d/scriv.ini. The set has no flake, so its scriv comes from the pslua dev shell.

This is the canon half of purescript-lua/purescript-lua#101. The forks carry the matching scaffold in their own repos.

Records the ecosystem-wide decision to keep changelogs with scriv, reversing
the no-changelog clause of ADR 0006:

- ADR 0009 (the new record), an ADR 0006 status note, and the ADR index entry.
- CONTRIBUTING gains a Changelogs section and a scriv collect step in the
  release flow.
- The set's own scriv-managed CHANGELOG.md, backfilled with the psc-* releases,
  plus changelog.d/scriv.ini. scriv for this repo comes from the pslua dev shell.

Part of purescript-lua/purescript-lua#101 (ecosystem-wide changelogs).

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the package-set ecosystem documentation to adopt scriv-managed changelogs (per new ADR 0009), addressing the discoverability gap created by the recent high-volume fork/FFI work where release notes were otherwise only aggregated in package-set bump commits.

Changes:

  • Adds ADR 0009 documenting the decision to manage CHANGELOG.md via scriv across the ecosystem, and indexes it in the ADR README.
  • Updates ADR 0006 status notes to reflect the changelog decision as a superseded clause.
  • Introduces a scriv-managed root CHANGELOG.md for this repository plus changelog.d/scriv.ini, and updates CONTRIBUTING with the new changelog + release steps.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
docs/adr/README.md Adds ADR 0009 to the ADR index.
docs/adr/0009-changelogs-via-scriv.md New ADR defining scriv-based changelog policy and release workflow implications.
docs/adr/0006-fork-release-by-annotated-tag.md Notes that ADR 0006’s no-changelog clause is superseded by ADR 0009.
CONTRIBUTING.md Documents scriv fragment workflow and adds scriv collect to the release process.
CHANGELOG.md Adds a scriv-managed changelog seeded/backfilled with recent psc-* set releases.
changelog.d/scriv.ini Adds scriv configuration for Markdown changelog collection.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Unisay Unisay merged commit 05a41ae into master Jun 25, 2026
3 checks passed
@Unisay Unisay deleted the issue-101/changelog-canon branch June 25, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants