From 19c6785ef0f22b311dd95cfea0f8b9957b7e0c7a Mon Sep 17 00:00:00 2001 From: Dan Wolfson Date: Tue, 13 Oct 2026 21:48:15 -0500 Subject: [PATCH] chore(release): bump version to 6.2.3 Ships the completed fixes now; the Egeria-blocked delete re-tests move to the next release (BACKLOG.md). Signed-off-by: Dan Wolfson --- BACKLOG.md | 4 +--- pyproject.toml | 2 +- uv.lock | 2 +- 3 files changed, 3 insertions(+), 5 deletions(-) diff --git a/BACKLOG.md b/BACKLOG.md index a726f0ac..77db0989 100644 --- a/BACKLOG.md +++ b/BACKLOG.md @@ -15,9 +15,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, then do the held 6.2.3 release. The owner wants outstanding issues fixed before releasing. - **The 6.2.3 release notes must list this behaviour change:** ISSUE-148. `AssetMaker.find_processes`, `get_processes_by_category`, `get_action_targets`, `get_actions_for_action_target`, `get_assigned_actions`, `get_actions_for_sponsor` and `get_actions_for_requester` now default `activity_status_list` to `None` (no filter) instead of `["IN_PROGRESS"]`. A caller that relied on getting only in-progress actions by default now also gets completed, cancelled and status-less actions (e.g. journal entries), so it should pass `["IN_PROGRESS"]` explicitly. - **Also list this API removal:** ISSUE-151. `AutomatedCuration.get_engine_actions()` is removed, because the View Server has no list-all endpoint for it (it always got a 404). Use `find_engine_actions("*")` instead. +3. Update each `PYEGERIA_ISSUES.md` entry with the result, and include any fixes in the next release after 6.2.3. (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 fee37c07..bba98977 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -3,7 +3,7 @@ [project] name = "pyegeria" -version = "6.2.2" +version = "6.2.3" 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 3868d990..96d31a6d 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.2" +version = "6.2.3" source = { editable = "." } dependencies = [ { name = "altair" },