Skip to content

Dispatch downstream version bumps on npm publish#1586

Open
Topherhindman wants to merge 1 commit into
mainfrom
chore/dispatch-downstream-bumps
Open

Dispatch downstream version bumps on npm publish#1586
Topherhindman wants to merge 1 commit into
mainfrom
chore/dispatch-downstream-bumps

Conversation

@Topherhindman
Copy link
Copy Markdown
Contributor

@Topherhindman Topherhindman commented May 22, 2026

Description

After changesets/action successfully publishes one or more packages, fires a repository_dispatch to TARGET_REPO with the publishedPackages JSON payload so we can open a PR bumping the pinned @livekit/agents-js versions in downstream consumers (agent-starter-node).

Only fires when steps.changesets.outputs.published == 'true', i.e. on the publish run that follows a merged release PR — not on runs that only open/update the release PR.

Pre-Review Checklist

  • Build passes: All builds (lint, typecheck, tests) pass locally
  • AI-generated code reviewed: Removed unnecessary comments and ensured code quality
  • Changes explained: All changes are properly documented and justified above
  • Scope appropriate: All changes relate to the PR title, or explanations provided for why they're included
  • Video demo: A small video demo showing changes works as expected and did not break any existing functionality using Agent Playground (if applicable)

Testing

  • Automated tests added/updated (if applicable)
  • All tests pass
  • Make sure both restaurant_agent.ts and realtime_agent.ts work properly (for major changes)

Additional Notes


Note to reviewers: Please ensure the pre-review checklist is completed before starting your review.

After changesets/action successfully publishes one or more packages,
fires a repository_dispatch to TARGET_REPO with the publishedPackages
JSON payload so internal-actions can open a PR bumping the pinned
@livekit/agents-js versions in downstream consumers (agent-starter-node).

Only fires when steps.changesets.outputs.published == 'true', i.e. on
the publish run that follows a merged release PR — not on runs that
only open/update the release PR.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 22, 2026

⚠️ No Changeset found

Latest commit: 1eac2f7

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

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

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