Skip to content

chore(main): release E4A.PostGuard 0.5.1#38

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--E4A.PostGuard
Open

chore(main): release E4A.PostGuard 0.5.1#38
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--E4A.PostGuard

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.5.1 (2026-07-24)

Bug Fixes

  • emit inclusive range-end in Cryptify Content-Range header (#34) (73c2e43), closes #28
  • harden ZIP entry-name handling in ZipHelper (#42) (2ffe84e)
  • reject duplicate recipient policy keys in BuildPolicyJson (#48) (f5ad9b8)
  • stop leaking raw upstream body in NetworkException (#41) (#43) (135dee3)

This PR was generated with Release Please. See documentation.

@dobby-coder

dobby-coder Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Dobby looked at this but isn't routing it anywhere: This PR was opened by github-actions bot via Release Please automation not a human so it should be dropped. If that's wrong, ping Dobby again or be explicit with /dobby review, /dobby fix, or /dobby ask.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--E4A.PostGuard branch 2 times, most recently from 16f9e3b to f4757b7 Compare July 10, 2026 08:35
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--E4A.PostGuard branch from f4757b7 to ec83222 Compare July 15, 2026 07:25
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--E4A.PostGuard branch from ec83222 to 3e45114 Compare July 22, 2026 08:18
@dobby-coder
dobby-coder Bot requested a review from Iso5786 July 23, 2026 11:21
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--E4A.PostGuard branch from 3e45114 to 393eca5 Compare July 24, 2026 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Content-Range chunk-upload header uses exclusive end byte (off-by-one)

0 participants