Repository navigation
Merge v17/main into v18/main (2026-10-26) - #1146
Merged
Merged
Conversation
The Azure DevOps npm feed stops being anonymously readable in 2027, and
@jumoo/usync 17.5.0 / 18.2.0 were never published anywhere. Both are now
on npmjs.org (published by hand from the release tags); this moves the
workflows over so future releases and nightlies publish there.
- usync-assets: publishConfig is now { access: public }, no Azure registry
- release.yml: npm publish step (trusted publishing, per-major dist-tags:
latest / latest-{major} / next-{major}); builds ./dist with client:build
- prerelease.yml: version from the release-tag walk,
{next patch}-prerelease.{run}, instead of GitVersion; publishes to
next-{major}; id-token: write
- remove GitVersion.yml and its dependabot pin (no longer used)
- history-client: drop the .npmrc pointing @Jumoo at Azure; lock entries
for @jumoo/usync (17.5.0) and @jumoo/translate (17.10.0) now resolve
from npmjs.org
- usync-assets lock: 17 packages that resolved through the Azure feed's
npmjs proxy now resolve from npmjs.org directly (same tarballs)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Publish @jumoo/usync to npmjs.org with trusted publishing
- #1143 Publish @jumoo/usync to npmjs.org with trusted publishing Conflicts resolved: - prerelease.yml: took v17's tag-walk version step (replaces the v18/main GitVersion branch check); example comment set to v18 - GitVersion.yml: deleted (no longer used) - lock files: kept v18's, then pointed the history-client's @jumoo/usync at 18.2.0 on npmjs.org and moved usync-assets' 13 Azure-proxied entries to npmjs.org (same tarballs) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Brings #1143 (publish
@jumoo/usyncto npmjs.org with trusted publishing) forward to v18.Baseline: #1142's merge commit, which already had all of v17/main up to 0fc4dd9. Carried 1 PR, nothing dismissed.
Conflicts / v18-specific
prerelease.yml: v17's tag-walk version step replaces v18's GitVersion +refs/heads/v18/maincheck. Nightlies become18.2.1-prerelease.{run}on npmnext-18.GitVersion.yml: deleted (v18 had its own edits; nothing uses it now).@jumoo/usync18.0.3 (Azure only) → 18.2.0 on npmjs.org. v18's history-client doesn't use@jumoo/translate.usync-assets/package.jsonversion untouched (CI stamps it).Checked locally:
npm ci && npm run buildin both clients, plusclient:build. No.npmrc,package.jsonor lock file references Azure.Please merge with a merge commit, not a squash, so the next forward port keeps its baseline.
🤖 Generated with Claude Code