Version Packages - #1399
Version Packages#1399
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Please upload reports for the commit 26ba506 to get more accurate results. Additional details and impacted files@@ Coverage Diff @@
## master #1399 +/- ##
=======================================
Coverage 91.59% 91.59%
=======================================
Files 127 127
Lines 4163 4163
Branches 1040 1040
=======================================
Hits 3813 3813
Misses 350 350
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
## Summary Manual version bump (the `Changeset Release Creator` bot is still broken -- see #1399 for the ongoing org-level Actions allow-list issue). Same as before: ran `yarn update-versions-and-changelogs` against the one changeset currently pending on `master`, from #1400 (removing the `resolveAnonymousIdConflicts` opt-in flag, making cross-subdomain `anonymousId` reconciliation unconditional). `@segment/analytics-next` bumps `1.84.2` -> `1.84.3`. Merging this (commit message starts with `Version Packages`) triggers `publish.yml`'s `should-release` check on push to `master`, which runs the real npm publish + CDN deploy. ## Test plan - [x] Relevant test suites pass (`src/generated`, `src/core/user`, `src/core/storage`) - [x] `tsc --noEmit` clean - [x] Verified `packages/browser/src/generated/version.ts` and `package.json` both read `1.84.3` - [x] Verified the generated `CHANGELOG.md` entry attributes #1400 correctly
Summary
Manual version bump, standing in for the
Changeset Release Creatorworkflow — that workflow has had a 100%startup_failurerate on every trigger since 2026-07-15 (the last successful run was 2026-04-29), so no "Version Packages" PR has been auto-created since then. That's an existing infra issue independent of this change; someone with org Actions-policy access should look into whyrelease-creator.ymlfails at startup.This is exactly what that bot would have produced: ran
yarn update-versions-and-changelogsagainst the two changesets currently pending onmaster:resolveAnonymousIdConflictsopt-in fix)@segment/analytics-nextbumps1.84.1->1.84.2.Merging this (commit message starts with
Version Packages) will makepublish.yml'sshould-releasecheck pass on push tomaster, triggering the real npm publish + CDN deploy.Test plan
packages/browsertest suite passes (849 passed, 4 pre-existing skips)tsc --noEmitcleanpackages/browser/src/generated/version.tsandpackage.jsonboth read1.84.2CHANGELOG.mdentry attributes both PRs correctly