Skip to content

Version Packages - #1399

Merged
abueide merged 1 commit into
masterfrom
version-packages-manual
Sep 11, 2026
Merged

abueide merged 1 commit into
masterfrom
version-packages-manual

Conversation

@abueide

@abueide abueide commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Manual version bump, standing in for the Changeset Release Creator workflow — that workflow has had a 100% startup_failure rate 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 why release-creator.yml fails at startup.

This is exactly what that bot would have produced: ran yarn update-versions-and-changelogs against the two changesets currently pending on master:

@segment/analytics-next bumps 1.84.1 -> 1.84.2.

Merging this (commit message starts with Version Packages) will make publish.yml's should-release check pass on push to master, triggering the real npm publish + CDN deploy.

Test plan

  • Full packages/browser test suite passes (849 passed, 4 pre-existing skips)
  • tsc --noEmit clean
  • Verified packages/browser/src/generated/version.ts and package.json both read 1.84.2
  • Verified the generated CHANGELOG.md entry attributes both PRs correctly

@changeset-bot

changeset-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 26ba506

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codecov

codecov Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.59%. Comparing base (e7592fb) to head (2b154a7).
⚠️ Report is 1 commits behind head on master.

⚠️ Current head 2b154a7 differs from pull request most recent head 26ba506

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           
Flag Coverage Δ
browser 92.50% <100.00%> (ø)
core 90.07% <ø> (ø)
node 89.43% <ø> (ø)

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@abueide
abueide merged commit 53d0a6b into master Sep 11, 2026
35 of 37 checks passed
@abueide
abueide deleted the version-packages-manual branch September 11, 2026 16:20
@abueide abueide mentioned this pull request Sep 11, 2026
4 tasks
abueide added a commit that referenced this pull request Sep 11, 2026
## 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
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.

2 participants