Skip to content

bump keria version to 0.2.0, upgrade to keri 1.2.12#421

Closed
kentbull wants to merge 2 commits intoWebOfTrust:mainfrom
kentbull:release-prep-0.2.0
Closed

bump keria version to 0.2.0, upgrade to keri 1.2.12#421
kentbull wants to merge 2 commits intoWebOfTrust:mainfrom
kentbull:release-prep-0.2.0

Conversation

@kentbull
Copy link
Copy Markdown
Collaborator

Bump to version 0.2.0, upgrade keri to 1.2.12, and update various other dependencies.

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.74%. Comparing base (4e954a0) to head (5e27582).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #421   +/-   ##
=======================================
  Coverage   87.74%   87.74%           
=======================================
  Files          26       26           
  Lines        5808     5808           
=======================================
  Hits         5096     5096           
  Misses        712      712           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@daidoji
Copy link
Copy Markdown
Contributor

daidoji commented Mar 13, 2026

Should it be 0.2.0? On qvi-software GLEIF has it tagged as 0.3.0. It probably should increment a major version as there are API changes right? https://github.com/GLEIF-IT/qvi-software?tab=readme-ov-file#gleif-tested-versions-for-technical-dry-runs

@kentbull
Copy link
Copy Markdown
Collaborator Author

Yeah, it would be confusing to have a lower version number than the GLEIF version number. If we're okay with it then I suggest we move to v0.4.0, just to clear things up.

Thoughts @lenkan and @iFergal ?

@kentbull
Copy link
Copy Markdown
Collaborator Author

@daidoji I didn't think there were API changes. If there are then we should do a major version tick to 1.0

@daidoji
Copy link
Copy Markdown
Contributor

daidoji commented Mar 16, 2026

I don't know about API changes but does this version communicate with old witnesses?

Like 0.2.0 worked with keri witnesses on 1.2.6 but I've been having trouble getting those witnesses to work with main.

@kentbull
Copy link
Copy Markdown
Collaborator Author

you know what, let's just eliminate confusion and go with 0.4.0.

Any objections, @daidoji, @iFergal, or @lenkan? I'll close this PR and resubmit a 0.4.0 one.

@kentbull
Copy link
Copy Markdown
Collaborator Author

Succeeded by #422

@kentbull kentbull deleted the release-prep-0.2.0 branch March 16, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants