@@ -20,30 +20,17 @@ Pull the latest changes on `main` and run the release task:
2020``` sh
2121git checkout main
2222git pull
23- uv run poe release
2423```
2524
26- This runs the following steps automatically :
25+ You need to run the following commands :
2726
28- 1 . ` semversioner release ` -- consumes all pending change files and bumps the
29- version.
30- 2 . Regenerates ` CHANGELOG.md ` .
31- 3 . Updates ` project.version ` in every package's ` pyproject.toml ` .
32- 4 . Updates cross-package dependency version pins (e.g. ` graphrag-common==X.Y.Z `
33- in all packages that depend on it).
34- 5 . Runs ` uv sync --all-packages ` to update the lockfile.
35-
36- ### Cutting a release on Windows
37-
38- ` uv run poe release ` does not work on Windows unless you are using WSL. Poe
39- defaults to ` cmd.exe ` and there is no straightforward way to force it to use
40- PowerShell. Run each step manually in PowerShell instead:
41-
42- ``` powershell
27+ ``` zsh
4328uv run semversioner release
4429uv run semversioner changelog > CHANGELOG.md
4530
31+ # verify if the version is correct
4632$version = uv run semversioner current-version
33+ # check this only on Windows:
4734if (-not $version ) { Write-Error " Failed to get version" ; exit 1 }
4835
4936uv run update-toml update --file packages/graphrag/pyproject.toml --path project.version --value $version
@@ -65,11 +52,11 @@ Check `CHANGELOG.md` or any package's `pyproject.toml` to find the new version,
6552then move the changes to a release branch:
6653
6754```sh
68- git switch -c release/vVERSION
55+ git switch -c release/v<VERSION>
6956git add .
70- git commit -m " Release vVERSION "
71- git tag -a vVERSION -m " Release vVERSION "
72- git push origin release/vVERSION -u
57+ git commit -m "Release v<VERSION> "
58+ git tag -a v<VERSION> -m "Release v<VERSION> "
59+ git push origin release/v<VERSION> -u
7360```
7461
7562Open a PR targeting `main`. CI checks (semver, linting, tests) will run
0 commit comments