Skip to content

Rename and expose key material#689

Open
lehins wants to merge 4 commits into
masterfrom
lehins/rename-and-expose-key-material
Open

Rename and expose key material#689
lehins wants to merge 4 commits into
masterfrom
lehins/rename-and-expose-key-material

Conversation

@lehins

@lehins lehins commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

Description

See #688 for original intent that is being solved by this PR.

It is probably easier to review this PR one commit at a time

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
    New section is never added with the code changes. (See RELEASING.md)
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated.
    If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • Self-reviewed the diff

lehins added 3 commits July 14, 2026 17:15
This was mentioned in #679
But we need to do it now, since it would be useful to export safe parts
of it, which will be done in a follow up commit
@lehins lehins force-pushed the lehins/rename-and-expose-key-material branch from fe4a9d0 to 3f30c2d Compare July 14, 2026 14:15
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.

1 participant