diff --git a/.github/workflows/build-package.yaml b/.github/workflows/build-package.yaml
index dd62f89d..79771125 100644
--- a/.github/workflows/build-package.yaml
+++ b/.github/workflows/build-package.yaml
@@ -130,13 +130,13 @@ jobs:
         id: version
         env:
           # The open line, which is the one previews belong under - not the last one released.
-          # The line has released through v0.43.0-rc1000; there was no 0.7.0, and 0.23.0 through
+          # The line has released through v0.44.0-rc1000; there was no 0.7.0, and 0.23.0 through
           # 0.29.0 were skipped so the consolidation got a number of its own.
           #
           # This sat at 0.23.0 for the whole of v0.30.0-rc1000, so every preview that release
           # opened was stamped below it and the feed had nothing that could supersede the release.
           # It now moves in the same pull request as the tag it opens the line after.
-          RELEASE_LINE: 0.44.0
+          RELEASE_LINE: 0.45.0
         run: |
           VERSION="$RELEASE_LINE-preview$(printf '%06d' "$GITHUB_RUN_NUMBER")"
           echo "version=$VERSION" >> "$GITHUB_OUTPUT"
diff --git a/AGENTS.md b/AGENTS.md
index b59165eb..79c115f4 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -308,7 +308,7 @@ unmeasured rather than untested.
 ## Releasing
 
 A `v*` tag drives `release.yaml`, and the tag is the source of truth for the version. The current
-line is `0.43.0-rc1000`; there was no 0.7.0, and 0.23.0 through 0.29.0 were skipped. Do not
+line is `0.44.0-rc1000`; there was no 0.7.0, and 0.23.0 through 0.29.0 were skipped. Do not
 describe versions as `1.0.0-*`.
 
 **The release pull request is three edits.** `hardened` in `docs/.vitepress/version.json`, the
diff --git a/docs/.vitepress/version.json b/docs/.vitepress/version.json
index 89e83bbb..ce90470d 100644
--- a/docs/.vitepress/version.json
+++ b/docs/.vitepress/version.json
@@ -1,3 +1,3 @@
 {
-  "hardened": "0.43.0-rc1000"
+  "hardened": "0.44.0-rc1000"
 }