Repository navigation
chore(release): bump version to 6.1.8 - #333
Merged
Merged
Conversation
Ships the ISSUE-79 survey governance-action-type naming fix (automated_curation.py, PR odpi#324) -- confirmed via diffing the published 6.1.7 wheel that it's the only unreleased code change since 6.1.7. 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
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.
Summary
Ships the ISSUE-79 survey governance-action-type naming fix
(
automated_curation.py, #324) -- confirmed by diffing the actualpublished 6.1.7 wheel against current
mainthat it's the only unreleasedcode change since 6.1.7 (everything else merged since then is docs or
.github/workflow config, neither of which ships in the wheel).Also confirmed this pass:
egeria-python's own Dr.Egeria templates andreport specs have zero drift from the compact command JSON (
refresh_specs --merge-reportsproduced a byte-identical regeneration) -- the "templatesare out of date" report that prompted this traced to the downstream
mirrors in
egeria-workspaces-fsandtrellis/packages/egeria-advisor(~129 stale files each), now re-synced separately in those repos.
Testing
pytest tests/micro-tests/-- full pass. Onlypyproject.toml/uv.lockchanged (version bump).
Next step (not in this PR)
Once merged, tag
v6.1.8on the merge commit and push the tag to triggerthe actual release workflow (test -> build -> Trusted Publishing to PyPI
-> auto GitHub Release) -- the first time this repo's release process has
gone through that pipeline end-to-end in a while, rather than a manual
local publish.
🤖 Generated with Claude Code