From b5da5fd4e87ee3ecd4b763524c53f7cd39e5b178 Mon Sep 17 00:00:00 2001 From: Matt McKay Date: Fri, 15 May 2026 11:13:08 +1000 Subject: [PATCH] chore(quantecon): cut qe-v3 (book-proof-scope, #28) Bumps qe_version to qe-v3 and sets `tag: qe-v3` on the book-proof-scope entry. The git tag qe-v3 will be cut on the squash commit of this PR so that `cat VERSION.yml` at the tag is self-consistent (qe_version matches the tag). Per quantecon/README.md: "Doing it in this order means anyone who `cat`s VERSION.yml at tag qe-v sees a self-consistent file." Co-Authored-By: Claude Opus 4.7 --- quantecon/README.md | 12 +++++++----- quantecon/VERSION.yml | 4 ++-- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/quantecon/README.md b/quantecon/README.md index 7aa1b965f..2881aafbc 100644 --- a/quantecon/README.md +++ b/quantecon/README.md @@ -15,13 +15,15 @@ Two tracked YAML files in `quantecon/` record orthogonal facts. Keep them in syn ### Maintaining `VERSION.yml` -Every time a feature PR lands on `main`, append a row to `merged_features` with its squash `merge_sha`. The `tag` field stays null until the next `qe-v` checkpoint. +Every time a feature PR lands on `main`, append a row to `merged_features` with its squash `merge_sha`. The `tag` field stays null until a `qe-v` tag is cut over that feature. -Tags are cut at meaningful checkpoints, **not per-PR** — typically when a batch of features is ready for downstream dogfooding. To cut a tag: +Tags can be cut per-PR (one tag per feature, easy traceability) or batched at a checkpoint (one tag covering several merged features ready for downstream dogfooding) — pick whichever fits the cadence. To cut a tag, do the metadata update *first* so the tagged commit's tree is self-consistent: -1. Pick the `main` commit at the head of the batch -2. Tag it: `git tag qe-v -m "qe-v: "` then `git push origin qe-v` -3. Set `tag: qe-v` on each newly-included feature in `merged_features` and bump `qe_version` +1. Open a doc PR updating `VERSION.yml`: bump `qe_version` to `qe-v` and set `tag: qe-v` on each previously-untagged entry in `merged_features` that is included in this tag. +2. Squash-merge the doc PR. +3. Tag the resulting `main` commit: `git tag qe-v -m "qe-v: "` then `git push origin qe-v`. + +Doing it in this order means anyone who `cat`s `VERSION.yml` at tag `qe-v` sees a self-consistent file (qe_version field matches the tag). ### Maintaining `UPSTREAM-PRS.yml` diff --git a/quantecon/VERSION.yml b/quantecon/VERSION.yml index 18104ba8c..eab42a1dd 100644 --- a/quantecon/VERSION.yml +++ b/quantecon/VERSION.yml @@ -24,7 +24,7 @@ # `merged_features` that is included in the batch, then bump # `qe_version` to `qe-v` -qe_version: qe-v2 +qe_version: qe-v3 upstream_base: 1.9.0 merged_features: @@ -47,4 +47,4 @@ merged_features: description: Section-level scope for proof:* / figure / equation auto-prefix local_pr: 28 merge_sha: 80bb9ecf - tag: null # cut at next qe-v checkpoint + tag: qe-v3