Skip to content

chore(deps): update dependency postal-mime to 3.0.0 - #2311

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
buddy-bot/update-major-update-postal-mime
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
buddy-bot/update-major-update-postal-mime

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

npm

Package Change Age Adoption Passing Confidence
postal-mime (source) 2.7.6 -> 3.0.0 age adoption passing confidence

Release Notes

postalsys/postal-mime (postal-mime)

2.7.6 -> 3.0.0

v3.0.0

Compare Source

3.0.0 (2026-08-11)

⚠ BREAKING CHANGES

  • header values in headers[].value keep the whitespace that folding introduced instead of having every whitespace run collapsed to a single space, single value headers such as subject and from resolve to the first occurrence of a duplicated header rather than the last, and to, cc, bcc and replyTo are returned in document order rather than reversed.

Bug Fixes

  • resolve non-WHATWG charset labels instead of falling back to windows-1252 (6378618), closes #94
  • unfold headers per RFC 5322 and resolve duplicated headers first-wins (7b0ca9d)

Released by github-actions[bot] on 8/11/2026


📊 Package Statistics

  • postal-mime: npm package with weekly downloads tracked on npmjs.com

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Buddy 🤖

@glennmichael123

Copy link
Copy Markdown
Member

Closing as obsolete rather than rebasing.

postal-mime is no longer declared in storage/framework/core/email/package.json, and git grep finds no reference to postal-mime or PostalMime in any tracked file. It does not appear in bun.lock either.

The patch therefore applies to a line that no longer exists, which is why it went stale. The copy still sitting in node_modules is an unpruned leftover from before the dependency was dropped, not something the build resolves.

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.

1 participant