Skip to content

chore: merge develop into main - #600

Merged
MaksymStoianov merged 2 commits into
mainfrom
develop
Nov 17, 2026
Merged

MaksymStoianov merged 2 commits into
mainfrom
develop

Conversation

@MaksymStoianov

Copy link
Copy Markdown
Member

Brings the release tag change (#599) to main: release-please tags releases as vX.Y.Z and the publish step skips a version already on npm.

After this merge release-please updates the open release PR #584 to 3.0.0 with the tag v3.0.0. Order from there: merge #584 → publish @bootgs/utils@3.0.0 by hand → add the trusted publisher on npmjs.com → run release-please by hand with tag v3.0.0 to attach the signed tarball and SBOM.

🤖 Generated with Claude Code

MaksymStoianov and others added 2 commits November 17, 2026 23:04
…version

release-please drops the component from the tag (v3.0.0, as in bootgs/boot);
last-release-sha points at apps-script-utils-v2.1.1 so the next changelog
starts there (remove it after the first v* release). The publish step skips
a version that is already on npm, so a release published by hand still
gets its signed tarball and SBOM on the GitHub release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Maksym Stoianov <stoianov.maksym@gmail.com>
ci(release): tag releases as vX.Y.Z, skip npm publish of an existing version
@MaksymStoianov
MaksymStoianov merged commit 84a12f5 into main Nov 17, 2026
10 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