Repository navigation
ci(tools): publish 2.x patches from release/tools-2.x under the legacy-2 dist-tag - #1825
Merged
Merged
Conversation
…y-2 dist-tag Release-branch-only change. Pushes to release/tools-2.x that touch packages/tools/package.json or this workflow publish through the same trusted-publishing workflow file, with --provenance and --tag legacy-2 so 'latest' (3.x) never moves. The version check now looks up the exact local version instead of comparing against 'latest', skips versions that already exist, refuses anything that is not 2.x, and fails closed if npm cannot be queried. Unit tests run before publish. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | 274a1d8 | Oct 16 2026, 11:08 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 274a1d8 | Commit Preview URL Branch Preview URL |
Oct 16 2026, 11:10 PM |
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
1 participant
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.
This changes
publish-tools.ymlonrelease/tools-2.xonly, so that 2.3.1 (the scope fix from #1824) can be published from this branch. Nothing onmainchanges: main's copy of the workflow keeps publishing 3.x tolatest.Merging this PR publishes
@supermemory/tools@2.3.1to npm under thelegacy-2dist-tag.Changes
release/tools-2.xinstead ofmain. The path filter also covers this workflow file, so the merge itself triggers the first run.npm publish --access public --provenance --tag legacy-2. Because the tag is explicit, publishing can't movelatest, which stays on 3.1.2. Provenance and OIDC trusted publishing still work, because the workflow file name is unchanged and npm ties the trusted publisher to the file name, not the branch.npm view <pkg>@<version>) instead of comparing againstlatest. The old comparison would always see 3.1.2 and try to publish again.bun install --frozen-lockfileand atest:unitrun before publish.What a later push does
packages/tools/package.jsonor this workflow file doesn't run the workflow at all.Verification
actionlintreports no errors on the workflow.2.3.1→changed=true2.3.0→changed=false("already published, skipping")3.1.2→ exit 1, "only publishes 2.x"bun install --frozen-lockfilereports no lockfile changes,bun run test:unitpasses 114/114, andbun run buildpasses.After the merge,
npm view @supermemory/tools dist-tagsshould showlatest: 3.1.2andlegacy-2: 2.3.1.