Introduce release flow inspired by changesets-bot#169
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This adds a system automated changelog/versioning/release infrastructure to the workspace which is similar to that of the changesets setup of vercel/vercel. Commits are now required to have towncrier fragments in them, which are then used to compose per-package changelog and determine the next version bump. Intra-workspace dependencies are automatically updated by the custom hatch hook on package build. Additionally, this finishes standardisation on `poe` for running repo scripts and top-level `poe test` can now be used to run repo-wide or scoped QA tasks. There is now a managed git hook system that automatically synchronizes local checkout's `.git/config` `hook.` entries to run scripts in `scripts/githooks/` and we run lint/typecheck on staged files pre-commit and a full qa suite on the commit pre-push. In both cases unstaged/uncommitted changes are excluded from the checks so commits are guaranteed to be self-consistent. Document the release process in RELEASING.md and also move development-related docs to CONTRIBUTING.md.
elprans
force-pushed
the
elprans/release-flow
branch
from
July 10, 2026 20:46
abb6e53 to
64b01d3
Compare
ricardo-agz
approved these changes
Jul 10, 2026
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
2 participants
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.
This adds a system automated changelog/versioning/release infrastructure
to the workspace which is similar to that of the changesets setup of
vercel/vercel.
Commits are now required to have towncrier fragments in them, which are
then used to compose per-package changelog and determine the next version
bump. Intra-workspace dependencies are automatically updated by the
custom hatch hook on package build.
Additionally, this finishes standardisation on
poefor running reposcripts and top-level
poe testcan now be used to run repo-wide orscoped QA tasks.
There is now a managed git hook system that automatically synchronizes
local checkout's
.git/confighook.entries to run scripts inscripts/githooks/and we run lint/typecheck on staged files pre-commitand a full qa suite on the commit pre-push. In both cases
unstaged/uncommitted changes are excluded from the checks so commits are
guaranteed to be self-consistent.
Document the release process in RELEASING.md and also move
development-related docs to CONTRIBUTING.md.