diff --git a/BACKLOG.md b/BACKLOG.md
index 467027dd..e5bb6f02 100644
--- a/BACKLOG.md
+++ b/BACKLOG.md
@@ -27,7 +27,7 @@ Once the Egeria release with the delete fixes is published and the local quickst
 1. **ISSUE-146:** re-test `remove_note`, which now posts to `metadata-expert/metadata-elements/{guid}/delete`, against test JournalEntry `8bec72e4-6da6-40a4-943e-d81e2173ec9b` on Erin's profile (`10dc7da9`). Try a plain delete first, then `deleteMethod: ARCHIVE` if it still fails with `OMAG-REPOSITORY-HANDLER-400-008`. Tell the egeria-workspaces-fs session before deleting anything on Erin's profile. Keep `fef83ed5` (owner's decision).
 2. **Other delete issues** to re-check at the same time: ISSUE-117 (Memento cascade delete), ISSUE-125 (`deleteEnumDef`) and ISSUE-132 (`cascadedDelete` field name).
    Also ISSUE-147, the valid-metadata clears: re-run the ISSUE-147 sequence (setup then clear for a value, a map name and a map value on a made-up property). Expect no 400-011 error after a successful clear, and expect the map value to actually be removed.
-3. Update each `PYEGERIA_ISSUES.md` entry with the result, and include any fixes in the next release after 6.2.4. (6.2.4, 2026-10-16, ships only the My Profile My Network work from #458; these re-tests are still blocked on Egeria. Owner, 2026-10-13: 6.2.3 ships now with the completed fixes instead of waiting for these re-tests, which are all blocked on Egeria. 6.2.3's release notes list the ISSUE-148 behaviour change and the ISSUE-151 API removal.)
+3. Update each `PYEGERIA_ISSUES.md` entry with the result, and include any fixes in the next release after 6.2.5. (6.2.4, 2026-10-16, shipped only the My Profile My Network work from #458. 6.2.5, same day, ships only the ISSUE-153 GovernanceEngine client from #460; its release notes must say that AutomatedCuration's engine-action methods are deprecated and now call the governance-engine view service, falling back to the old automated-curation path on a 404. These re-tests are still blocked on Egeria. Owner, 2026-10-13: 6.2.3 ships now with the completed fixes instead of waiting for these re-tests, which are all blocked on Egeria. 6.2.3's release notes list the ISSUE-148 behaviour change and the ISSUE-151 API removal.)
 
 ---
 
diff --git a/pyproject.toml b/pyproject.toml
index 5e268e75..57845ffa 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -3,7 +3,7 @@
 
 [project]
 name = "pyegeria"
-version = "6.2.4"
+version = "6.2.5"
 license = 'Apache-2.0'
 license-files = ["LICENSE"]
 authors = [{name = "Dan Wolfson", email = "dan.wolfson@pdr-associates.com"},]
diff --git a/uv.lock b/uv.lock
index 2c9e5e7d..5e79c56e 100644
--- a/uv.lock
+++ b/uv.lock
@@ -1875,7 +1875,7 @@ sdist = { url = "https://files.pythonhosted.org/packages/f8/f6/8f49005d581cff883
 
 [[package]]
 name = "pyegeria"
-version = "6.2.4"
+version = "6.2.5"
 source = { editable = "." }
 dependencies = [
     { name = "altair" },