Skip to content

docs(release): record the continuous-release model and the CI-skip gotcha#45

Merged
jimCresswell merged 1 commit into
mainfrom
chore/continuous-release-closeout
Jun 18, 2026
Merged

docs(release): record the continuous-release model and the CI-skip gotcha#45
jimCresswell merged 1 commit into
mainfrom
chore/continuous-release-closeout

Conversation

@jimCresswell

Copy link
Copy Markdown
Contributor

What & why

Closeout for #44 (continuous release on merge). Documentation/memory only.

  • continuity + program memory + napkin: the release-PR / --auto pattern is retired; releases are now continuous via the Oak Semantic Release Bot pushing the bump to protected main.
  • dev-tooling note: records the gotcha that bit feat(release): continuous release on merge via the Oak Semantic Release Bot #44 — a feature commit or PR message that quotes the CI-skip marker in prose makes the squash-merge skip CI, so no release fires. Only the bump commit should carry the marker.

Note

#44's own merge skipped CI for exactly that reason, so the first continuous release never fired and main is still 0.3.0. Merging this PR (its message is clean) is the first clean push to main since #44, so it should trigger the first continuous release — the computed minor v0.4.0 — and live-verify the bot's push to protected main.

🤖 Generated with Claude Code

…tcha

Closeout for PR #44 (continuous release on merge). Refresh continuity,
the program memory, and the napkin to reflect that the release-PR pattern
is retired in favour of the Oak Semantic Release Bot pushing the bump to
protected main, and document the gotcha that bit #44's own merge: a
feature commit or PR message that quotes the CI-skip marker in prose makes
the squash-merge skip CI, so no release fires. Adds a dev-tooling note so
template adopters avoid it.

Merging this (with a clean message) is the first clean push to main since
#44, so it should trigger the first continuous release (the computed minor,
v0.4.0) and verify the bot's push to protected main.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 18, 2026 13:15
@sonarqubecloud

Copy link
Copy Markdown

@github-code-quality

Copy link
Copy Markdown

Code Coverage Overview

Languages: Python

Python / code-coverage/pytest

The overall coverage remains at 89%, unchanged from the branch.


Code Coverage is in Public Preview. Learn more and provide us with your feedback.

@jimCresswell jimCresswell merged commit 7c7d452 into main Jun 18, 2026
8 checks passed
@jimCresswell jimCresswell deleted the chore/continuous-release-closeout branch June 18, 2026 13:16

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

Documents the post-#44 continuous-release-on-merge process and captures an operational gotcha where including GitHub’s CI-skip token in squash-merge text can prevent CI (and therefore prevent the release workflow from running).

Changes:

  • Adds a dev-tooling note warning to keep the CI-skip marker out of feature PR/commit messaging (only the bump commit should include it).
  • Updates repo continuity “program memory” to reflect the continuous release model and the fact it hasn’t yet been live-verified due to #44’s skipped CI.
  • Updates the active “napkin” session notes with the same continuity/gotcha context.

Reviewed changes

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

File Description
docs/dev-tooling.md Documents the CI-skip marker gotcha that can prevent the release workflow_run from firing under squash merge.
.agent/memory/operational/repo-continuity.md Updates operational continuity memory to record the new continuous release model and expected first release after a clean merge.
.agent/memory/active/napkin.md Captures session notes for #44’s continuous-release change and the CI-skip surprise for future reference.

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