From b7c5205db65c4b7e6d5714ff4044b7679fa1be21 Mon Sep 17 00:00:00 2001 From: Sahil Kumar Date: Wed, 21 Oct 2026 14:20:58 +0200 Subject: [PATCH] docs(repo): bump melos refs on every release Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_015FiDwZbppEqvx7gT93woZc --- .claude/skills/release-pr/SKILL.md | 10 +++++----- STYLE_GUIDE.md | 2 ++ 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/.claude/skills/release-pr/SKILL.md b/.claude/skills/release-pr/SKILL.md index e12f9c42..972c2fc4 100644 --- a/.claude/skills/release-pr/SKILL.md +++ b/.claude/skills/release-pr/SKILL.md @@ -136,12 +136,12 @@ Branch name: `release/-vX.Y.Z` for a single package, or `release/YYYY-MM-DD For **each** package being released: - Set `version: ` in `packages//pubspec.yaml`. +- Set its entry in `melos.yaml`'s `command.bootstrap.dependencies` block to `^` + (`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: diff --git a/STYLE_GUIDE.md b/STYLE_GUIDE.md index e7222878..45e2644c 100644 --- a/STYLE_GUIDE.md +++ b/STYLE_GUIDE.md @@ -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