chore(release): bump version to 6.2.6

BACKLOG.md

@@ -19,15 +19,15 @@ Mandy will expose more engine-host internal APIs as View Server REST calls once
 
 ## 🟡 Medium Priority — Re-test deletes when the new Egeria release lands
 
-**Status:** open, blocked on Egeria (its delete fixes are in progress upstream)
+**Status:** mostly done 2026-10-19. The quickstart was redeployed on Egeria `main` 05a5e982, and ISSUE-125, 132 and 147 (and 117's plain path) pass; results are in `PYEGERIA_ISSUES.md`. Still open: item 1 (ISSUE-146 `remove_note` on `8bec72e4`), not yet re-run; 117's Memento path is with Resource Explorer.
 **Added:** 2026-10-13
 
 Once the Egeria release with the delete fixes is published and the local quickstart is redeployed:
 
 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.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.)
+3. Update each `PYEGERIA_ISSUES.md` entry with the result, and include any fixes in the next release after 6.2.5. (6.2.6, 2026-10-19, ships the ISSUE-156 catalog-target and ISSUE-157 Service Level Objective fixes from #464; the re-tests needed no pyegeria change. 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.)
 
 ---
 

pyproject.toml

@@ -3,7 +3,7 @@
 
 [project]
 name = "pyegeria"
-version = "6.2.5"
+version = "6.2.6"
 license = 'Apache-2.0'
 license-files = ["LICENSE"]
 authors = [{name = "Dan Wolfson", email = "dan.wolfson@pdr-associates.com"},]