fix(release): HEAD~1 tags + trust empty state; ship tools@0.2.0-beta.1 - #76
Merged
Tanya7z merged 4 commits intoJul 25, 2026
Merged
Conversation
LSP: stop CI auto --from-existing (fetch-depth:0 should version-diff); empty .sfmc-release-tags.json must not fall back to scanning all tags. DRY: resolveReleaseTagEntries shared by push / gh-release. Co-authored-by: Shiroha <Tanya7z@users.noreply.github.com>
… ROOT Delete applied fix-release-tag-shallow.md; document empty-state/HEAD~1 in CHANGELOG. Extract remote-controller project-root.ts (align db/qq DIP). Co-authored-by: Shiroha <Tanya7z@users.noreply.github.com>
Wire optional PAT for Version PR when Actions cannot create PRs. Exclude pre.json consumed ids from listPendingChangesetFiles (pre mode). Co-authored-by: Shiroha <Tanya7z@users.noreply.github.com>
4 tasks
Tanya7z
marked this pull request as ready for review
July 25, 2026 05:50
Contributor
Author
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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
2 participants
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.
Summary
Post-merge review of
#73/#74onmain@2d7f763. ootb succeeded; changeset-release failed because Actions cannot create PRs (repo setting), leavingchangeset-release/mainwithout a Version Packages PR.This PR:
0.2.0-beta.1version bump (consumesfix-release-tag-shallow)#74leftremote-controllerROOT with db/qq (project-root.ts)Review findings → fixes
GitHub Actions is not permitted to create or approve pull requestsdocs/dev/npm-publish.md; this PR carries the Version Packages content so publish can proceed after merge--from-existingdespitefetch-depth: 0, re-listing all existingname@versiontagstag-packagesonly uses--from-existing/SFMC_TAG_FROM_EXISTING=1; default =HEAD~1diff.sfmc-release-tags.jsontreated as missing → fallback scanned all tagsresolveReleaseTagEntries: trust present state includingtags: []resolveReleaseTagEntriesremote-controllerinlined ROOTproject-root.tsTests
node --test tools/changeset-release.test.mjs— 7 pass (incl. empty-state LSP cases)Maintainer action (still needed)
Enable Settings → Actions → General → Allow GitHub Actions to create and approve pull requests, or future Version Packages PRs will keep failing the same way.
Residual (not in this PR)
ServiceIdpack-manager still registered