Skip to content

docs(repo): bump melos refs on every release #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xsahil03x merged 1 commit into from
Oct 22, 2026
+7 −5
Merged

docs(repo): bump melos refs on every release #201

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions .claude/skills/release-pr/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,12 +136,12 @@ Branch name: `release/<pkg>-vX.Y.Z` for a single package, or `release/YYYY-MM-DD
For **each** package being released:

- Set `version: <newver>` in `packages/<pkg>/pubspec.yaml`.
- Set its entry in `melos.yaml`'s `command.bootstrap.dependencies` block to `^<newver>`
(`grep -nE 'stream_(core|core_flutter|thumbnail):' melos.yaml`), replacing whatever range is there — even when the
old range already allows the new version. The block is the repo's record of the current version of each package,
and it is what `melos bootstrap` writes into every in-repo consumer's pubspec (the gallery, the thumbnail example).

Only if a released package is a **dependency that a dependent must now require at the new version** (the dependent
started using a new API), also bump that package's entry in `melos.yaml`'s `command.bootstrap.dependencies` block
(`grep -nE 'stream_(core|core_flutter|thumbnail):' melos.yaml`) — and release the dependent too. A compatible bump
that the existing caret already allows (e.g. `stream_core 0.4.0 → 0.4.1` under `stream_core: ^0.4.0`) needs **no**
block change.
If an in-repo dependent started using API that only exists in the new version, release that dependent too.

Then propagate constraints:

Expand Down
2 changes: 2 additions & 0 deletions STYLE_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1454,6 +1454,8 @@ heading to become `## X.Y.Z` on a `release/` branch. On that branch, for **each*
package you are releasing:

- bump its `version` in `pubspec.yaml`
- set its `melos.yaml` `command.bootstrap.dependencies` entry to `^X.Y.Z`, then
run `melos bootstrap` so in-repo consumers pick it up
- promote its CHANGELOG `## Upcoming` heading to `## X.Y.Z`

Title the PR `chore(repo): release packages` for a multi-package release
Expand Down
Loading