Repository navigation
chore(release): bump version to 6.2.5 - #461
Merged
Merged
Conversation
Ships the ISSUE-153 GovernanceEngine client (odpi#460). Egeria #9371 moved the engine-action operations to the governance-engine view service, so 6.2.4 and earlier get 404s from engine-action calls on current Egeria. AutomatedCuration's engine-action methods are now deprecated wrappers that call the new service and fall back to the old path on a 404. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps pyegeria to 6.2.5 to ship #460, the ISSUE-153 GovernanceEngine client.
Egeria #9371 moved the engine-action operations (claim, active-claimed, approved, status / action-target updates, completion status) to the new governance-engine view service, so on current Egeria pyegeria 6.2.4 and earlier get 404s from those calls.
pyproject.toml,uv.lock: 6.2.4 → 6.2.5BACKLOG.md: the Egeria-blocked delete re-tests carry over to the release after 6.2.5. The note also says what 6.2.5's release notes must cover: AutomatedCuration's engine-action methods are deprecated (DeprecationWarning), call the governance-engine view service, and fall back once to the old automated-curation path on a 404.Verified
uv run -p 3.13 pytest tests/micro-tests/: 1193 collected, 0 failedfrom pyegeria import GovernanceEngineworks, and the My Profile modules still import.active-claimed/approvedendpoints return 200.After merge: tag
v6.2.5onmainto triggerrelease.yml.🤖 Generated with Claude Code