Repository navigation
fix(version): untagged-package warning matches resolved changelog range - #749
Merged
Merged
Conversation
Fixes #727 Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Standing release PR: #730 · v0.42.1 queued (4 packages) · open 6h 22m · ✅ ready to merge Release Preview — v0.42.0 → v0.42.1
These changes will be added to the release PR (#730) when merged: Changelogmonorepo 0.42.0 → 0.42.1
After merge — predicted release
Updated automatically by ReleaseKit |
The resolved range is always `HEAD` or `<ref>..HEAD`, so the two branches differ only in the phrase naming the range. Restores the comment on why the warning exists, which moved with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… runs The old comment cited a 422 from an oversized standing-PR body, but the body has been truncated below GitHub's limit since the warning was added. The full-history test now sets the no-reachable-tag case explicitly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…arning Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With a manifest version, the processor never calls getLatestTag, so the global tag in the nearest-tag test had no effect. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 24, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The warning for a package with no tag of its own always said its changelog "will include the full git history". That's only true when no tag is reachable at all. Otherwise
BaselineResolverstarts the range at the nearest reachable tag, so in a tagged monorepo the warning overstated the problem.The warning now runs after the range is resolved, and describes it:
HEAD): "its changelog will include the full git history."<tag>..HEAD): "its changelog will start from<tag>."Both still suggest the
git tagcommand that sets a baseline. Runs with abaseRef, such as PR previews, still skip the warning.Related Issue(s)
Closes #727.
Type of Change
feat— New featurefix— Bug fixdocs— Documentation changerefactor— Code refactoringtest— Adding or updating testschore— Maintenance, dependencies, toolingScope
@releasekit/version@releasekit/notes@releasekit/publish@releasekit/release@releasekit/config@releasekit/coreChecklist
pnpm lint)pnpm test)pnpm typecheck)Testing Notes
processPackagestests cover both messages: full history when no tag is reachable, andstart from pkg-b@v1.0.0when one is. The second fails if the message ignores the resolved range.@releasekit/versiontypecheck, unit tests (747) and integration tests pass, andpnpm lintpasses.Made with Cursor
The PR appears safe to merge.Summary
Updates the untagged-package warning to describe the resolved changelog range.
No actionable issues found. Tests were inspected, not run.
Reviews (1) · Last reviewed commit: "fix(version): untagged-package warning m..." · Reviewed by Greptile