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

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.5.1 (2026-06-23)

Bug Fixes

  • emit inclusive range-end in Cryptify Content-Range header (#34) (73c2e43), closes #28

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.

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