Skip to content

chore: release v0.1.28#161

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-05-17T16-08-10Z
Open

chore: release v0.1.28#161
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-05-17T16-08-10Z

Conversation

@github-actions

@github-actions github-actions Bot commented May 17, 2026

Copy link
Copy Markdown
Contributor

🤖 New release

  • cryptify: 0.1.27 -> 0.1.28
Changelog

0.1.28 - 2026-06-04

Added

  • (email) remove circle around signer-verified checkmark (#173)
  • (email) replace unicode checkmark with inline PNG image (#172)
  • (email) staging-only /staging/preview/ + shared render API (#171)
  • (metrics) pre-seed known channels at zero on startup (#165)
  • expose Prometheus /metrics endpoint for usage dashboards (#102)

Fixed

  • (email) address postguard#197 deliverability + show disclosed signer name (#170)

Other

  • bump pg-core 0.6.0 → 0.6.1 (#164)
  • add semantic PR title check workflow (#162)


This PR was generated with release-plz.

@dobby-coder dobby-coder Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Standard release-plz bump from 0.1.27 to 0.1.28. Diff is limited to version bumps in Cargo.toml/Cargo.lock and a changelog entry for the dependency lockfile update. Looks good.

@github-actions github-actions Bot force-pushed the release-plz-2026-05-17T16-08-10Z branch 4 times, most recently from 8205f4a to 150b370 Compare May 18, 2026 17:24
@github-actions github-actions Bot force-pushed the release-plz-2026-05-17T16-08-10Z branch 3 times, most recently from a76126a to e2be385 Compare June 4, 2026 11:34
@github-actions github-actions Bot force-pushed the release-plz-2026-05-17T16-08-10Z branch from e2be385 to 43aa6ac Compare June 4, 2026 13:47
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.

0 participants