Skip to content

docs(changelog): promote Unreleased to 1.1.0 - #167

Merged
workshop-maybe merged 1 commit into
mainfrom
release/1.1.0
Sep 6, 2026
Merged

docs(changelog): promote Unreleased to 1.1.0#167
workshop-maybe merged 1 commit into
mainfrom
release/1.1.0

Conversation

@workshop-maybe

Copy link
Copy Markdown
Contributor

Promotes the accumulated ## [Unreleased] section — the quiz-assignment work from #166 — under ## [1.1.0] - 2026-09-06. No prose changes; the entries were written to ship.

Why minor, not patch. #166 adds a command (course import-assignment), a module-directory file (assignment.quiz.json) and an error kind (kind: verify). All additive, so semver says minor. A v1.0.1 tag advertising a new command would misread this file's own policy line and would leave the next genuine bugfix release without a natural number.

This also unblocks the release script. scripts/release.sh hard-exits (no bypass prompt) on a non-empty [Unreleased] with no versioned heading — exactly the state main is in now.

Verified scripts/changelog-section.sh 1.1.0 extracts the section cleanly and stops at the ## [1.0.0] boundary, so the GitHub release body will be the intended notes rather than commit subjects.

After merge: ./scripts/release.sh 1.1.0 from a synced main.

Known and deliberately not blocking — tracked in todos/039 (p2) and todos/040 (p3): the ON_CHAIN-module editability claim is derived from gateway/db-api source rather than a live preprod run, and the changelog entry says so in that same paragraph. The docs site (andamio-docs) does not cover import-assignment yet; separate repo, separate PR.

The quiz-assignment work (#165, #166) adds a command, a module-directory
file and an error kind — all additive, so this is a minor bump, not the
patch it might look like from "one feature". A 1.0.1 tag advertising a new
command would misread the policy line at the top of this file and leave
the next genuine bugfix release without a natural number.

Promoting the section is also what unblocks `scripts/release.sh`: its
preflight hard-exits on a non-empty [Unreleased] with no versioned
heading, which is exactly this state.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@workshop-maybe
workshop-maybe merged commit 35bd8da into main Sep 6, 2026
4 checks passed
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.

1 participant