Repository navigation
Release each package independently - #13
Merged
Merged
Conversation
The orchestrator is an ExaDev package, so it joins minimumReleaseAgeExclude alongside the other ExaDev packages.
…rchestrator release-workspace.config.ts replaces release.config.ts and keeps commit-types.ts as the single source for release rules and note sections, now with a test that holds the two in agreement. Release notes sections were previously configured under a `title` key the conventionalcommits preset does not read; they now use `section`, and a type that releases is never hidden. The release script runs the orchestrator, which commits every bump of a run once and pushes it with the tags before anything publishes.
…ator The release job runs `pnpm release`, which releases packages in dependency order with name@version tags and rewrites sibling pins. It keeps the GITHUB_TOKEN push credential, drops the ambient npm tokens in favour of OIDC trusted publishing, checks out main by name so pushes are not made from a detached HEAD, and upgrades npm to a release that supports trusted publishing.
README.md and CONTRIBUTING.md replace the whole-repository release description with the per-package model: dependency-ordered releases, name@version tags, sibling range rewrites, OIDC publishing, the one-time npm reservation and trusted publisher registration, and what a new package manifest needs.
The root package is private and never released, so a version in its manifest only goes stale once releases are decided per package.
Mearman
force-pushed
the
ci/per-package-releases
branch
from
October 10, 2026 10:22
d443d21 to
bfb4067
Compare
Mearman
marked this pull request as ready for review
October 10, 2026 10:25
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Replaces the whole-repo
semantic-releasesetup with@exadev/semantic-release-workspace, soprocess-graphand each@exadev/process-graph-*package version, tag and publish on their own, in dependency order. This is the upgrade path CONTRIBUTING.md already named.The release config is now
release-workspace.config.ts, still driven bycommit-types.ts, with a unit test tying the two together. Thereleasejob runspnpm releasewith OIDC trusted publishing hygiene and keepsGITHUB_TOKENas the push credential. npm is pinned to an exact release instead of@latest, as in the other ExaDev repos, so zizmor's ad-hoc install audit is ignored inline for that one step.A dry run from this branch lists dag, schema, domain, projection, then process-graph, each as 1.0.0 (no earlier
name@versiontags exist, so every package starts at 1.0.0).Not done here: the trusted publishers for the five package names are registered by the owner, and merging before they are makes the first CI publish fail the OIDC exchange.