Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/wneessen/go-mail from 0.6.0 to 0.6.1 #278

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 13, 2025

Bumps github.com/wneessen/go-mail from 0.6.0 to 0.6.1.

Release notes

Sourced from github.com/wneessen/go-mail's releases.

v0.6.1: Fix for multipart message rendering

Welcome to go-mail v0.6.1! This release is a bug-fix release that addresses a regression introduced in v0.6.0.

[!IMPORTANT]
If you are working with multipart messages and are currently using v0.6.0, it is advised to upgrade to v0.6.1 to avoid rendering issues.

Fix missing new-lines in multipart rendering

The v0.6.0 release introduced a regression in the multipart message generation (See #412). The boundary lines were not correctly seperated with a new line. This bug was introduced while working on the S/MIME handling. The issue has been fixed in #413. I am sorry for any inconveniences this might have caused. Thanks to @​Thomas2500 for reporting the issue!

Multipart boundary handling refactoring

While working on #412, I noticed a general issue with the boundary handling when fixed boundaries are set for the message. This bug was present already since the introduction of Msg.WithBoundary/Msg.SetBoundary, but was only brought to light with the new S/MIME feature introduced in v0.6.0. Since the S/MIME signing needs to set a fixed boundary, it was using the Msg.SetBoundary feature. If more than one multipart parts were used with a fixed boundary, this would render the mail broken (since it was using the same boundary for multiple parts). This has been fixed in #414 and #416. The GoDoc for Msg.WithBoundary/Msg.SetBoundary has also been updated with a warning that using the feature with more than one parts will break the message rendering.

Removal of XOAUTH2 from Auto-Discovery feature

Since XOAUTH2 works with Bearer tokens instead of passwords but the Auto-Discovery SMTP auth feature makes use of a username/password pair having XOAUTH2 in the prefered mechanisms list could cause authentication failures. Therefore the XOAUTH2 mechanism has been removed from the feature completely. Thanks to @​james-d-elliott for pointing this out!

What's Changed

Full Changelog: wneessen/go-mail@v0.6.0...v0.6.1

Commits
  • 559046e Merge pull request #418 from wneessen/chore/prepare-061-release
  • 47f46c5 Fix typos in test error messages
  • aaf22bb Fix typos in test case messages for server challenge assertions
  • 557691c Bump package version to 0.6.1
  • 9924b08 Merge pull request #417 from wneessen/bug/415_remove-xoauth-from-smtp-auth-au...
  • feb096f fix: Update SMTP auth preferences and adjust related tests
  • 1e0dea7 Merge pull request #416 from wneessen/bug/414_fixed-boundary-messes-up-multip...
  • ab6fc60 Refactor error assertion in S/MIME signing test
  • 7edbb75 Merge branch 'main' into bug/414_fixed-boundary-messes-up-multipart-rendering
  • 5ebfd47 Fix error messages and remove redundant test for rand.Reader
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/wneessen/go-mail](https://github.com/wneessen/go-mail) from 0.6.0 to 0.6.1.
- [Release notes](https://github.com/wneessen/go-mail/releases)
- [Commits](wneessen/go-mail@v0.6.0...v0.6.1)

---
updated-dependencies:
- dependency-name: github.com/wneessen/go-mail
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jan 13, 2025
@wneessen wneessen merged commit 40b826a into main Jan 13, 2025
6 checks passed
@wneessen wneessen deleted the dependabot/go_modules/github.com/wneessen/go-mail-0.6.1 branch January 13, 2025 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant