upgrade and prep: to KERIpy 1.2.14 and minimal strict tocks compat - #464
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #464 +/- ##
==========================================
+ Coverage 88.24% 88.26% +0.02%
==========================================
Files 26 26
Lines 5947 5950 +3
==========================================
+ Hits 5248 5252 +4
+ Misses 699 698 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
kentbull
marked this pull request as ready for review
September 14, 2026 19:34
kentbull
marked this pull request as draft
September 14, 2026 19:42
kentbull
force-pushed
the
chore/keripy-1.2.14
branch
from
September 14, 2026 19:45
0bc1480 to
18d20b1
Compare
Pin keri to 1.2.14 from PyPI and refresh its lockfile artifact. Retain hio 0.6.14, which satisfies the published KERIpy requirement of hio>=0.6.14. Reserve the existing KERIA Agent tock keys when resolving KERIpy cadences before Habery construction and reopening. Preserve legacy configuration without bypassing validation of KERIpy settings or dropping the tocks block. Test reopening with a checked-in legacy config file and real persisted Agent state, without patching LMDBer or Configer. Initial upgrade validation passed all 94 KERIA tests in Linux, Ruff checks, package builds, and CLI startup and shutdown. The revised real-file regression and two related configuration tests pass on macOS; the broader Agent run passes 22 tests with an existing fixed-identity collision reproduced in the original test.
kentbull
force-pushed
the
chore/keripy-1.2.14
branch
from
September 14, 2026 20:01
18d20b1 to
8945173
Compare
kentbull
marked this pull request as ready for review
September 15, 2026 02:33
Collaborator
Author
|
If possible will one of @daidoji @Arsh-Sandhu also review this PR? This is prep work for me to add the 100% tock configurability to KERIA, which will be the next PR. |
Collaborator
Author
|
I should say, this PR also pulls in the ESSR changes into KERIA that the Veridian team graciously contributed upstream to KERIpy. There are a number of things in the recently released |
kentbull
changed the title
iFergal
reviewed
Sep 15, 2026
daidoji
approved these changes
Sep 15, 2026
iFergal
approved these changes
Sep 15, 2026
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
3 participants
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.
PR Core:
keri 1.2.14 upgrade including minimal tocks compatibility with newly strict upstream KERIpy tock config validation
keri==1.2.14from PyPI.hio==0.6.14: the published KERIpy release requireshio>=0.6.14, rather than a newer exact HIO version. The lockfile changes only KERIpy and its artifact metadata.KERIpy 1.2.14 validates tock configuration strictly, so a dependency-only upgrade rejects existing KERIA configuration such as
{"tocks": {"escrower": 1.0}}, thus the need for the tock config work in this PR.Backwards compatibility for legacy flat tocks
Reserves the twelve existing KERIA Agent keys, now referred to as "legacy" tock config keys, when resolving KERIpy tocks before Agent Habery creation and reopening.
Preserves the original, legacy configuration for Agent consumers, while retaining KERIpy validation for new tock config and
cli -> env var -> config filebased override precedence.The test helper uses the same legacy config loading path.
Overall Tocks Plan
This is the prerequisite dependency PR for the planned KERIA tock configuration work coming after this PR merges. It does not yet introduce the KERIA registry, namespace migration to the new
"tocks.signify"subsection of the config file, deprecation warnings for using legacy tocks, runtime scheduling changes, or new performance defaults.