From b9c9861b0a936dce5286bb48ec4e9dca5c627161 Mon Sep 17 00:00:00 2001 From: PJ Date: Sun, 16 Aug 2026 15:17:05 +0530 Subject: [PATCH] docs(ci): say that the notes boundary is exclusive Measured against goreleaser 2.15.3: a first milestone's notes start after the first release rather than at it. Claude-Session: https://claude.ai/code/session_01ShuAy8q8ZfPi8KHxwc8JpQ --- docs/development/ci.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/development/ci.md b/docs/development/ci.md index ebd0159..a9423aa 100644 --- a/docs/development/ci.md +++ b/docs/development/ci.md @@ -315,6 +315,11 @@ level, so it reaches back to the first release there has ever been. A patch emit nothing, and an empty value leaves GoReleaser on the default that was already right for it. +The boundary is exclusive, the way a changelog always is: the notes cover what +landed *after* that tag. So the one release this shortchanges is the first +milestone of its kind, whose notes start after the first release rather than at +it. That is one merge, once, and it is not worth a special case. + ### The npm credential `NPM_TOKEN` is a classic automation token. Those do not expire, which is the