Skip to content

feat(ci): changesets release pipeline for visimer packages (#2872) - #10

Merged
inkeep-oss-sync[bot] merged 1 commit into
mainfrom
copybara/sync
Jul 24, 2026
Merged

feat(ci): changesets release pipeline for visimer packages (#2872)#10
inkeep-oss-sync[bot] merged 1 commit into
mainfrom
copybara/sync

Conversation

@inkeep-oss-sync

Copy link
Copy Markdown

Copybara-translated 1 Inkeep OSS change. Rebase-merge this PR so the prepared commit lands directly on public main.

Registers public-visimer as a release group and wires the same
cross-repo publish flow public-agents uses, sized down for a standalone
workspace:

- public-visimer-version-packages.yml (here): on main pushes touching
  public/visimer changesets or packages, runs changeset version and
  opens a Version Packages (visimer) PR. Single lockfile, no dual-lock
  contract, no root install needed.
- public/visimer/.github/workflows/release.yml (mirrors to
  inkeep/visimer): on main pushes with no pending changesets, builds and
  runs changeset publish --provenance via npm Trusted Publishing,
  verifies every @visimer/* package resolves on npm at the released
  version, then pushes the release tags.

No reverse repository_dispatch: nothing on agents-private hangs off a
visimer npm release (visimer.com deploys track main pushes, not npm), so
the failure surface is the run itself on inkeep/visimer.

release-groups:validate passes with the new group; CI.md workflow map
updated.
GitOrigin-RevId: 1d00f2a695cf18c3e908d235c7059454f43e194b
@inkeep-oss-sync
inkeep-oss-sync Bot merged commit b785cc3 into main Jul 24, 2026
@inkeep-oss-sync
inkeep-oss-sync Bot deleted the copybara/sync branch July 24, 2026 10:40
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