Merge branch 'release/0.13.4'

[jpnurmi]

The release bot failed to merge release/0.13.4 into master.

Not 100% sure what went wrong. There are no conflicts in CHANGELOG.md. Only #1604 and #1605 were merged while the release was running. Possibly related to:

Error: fatal: could not read Username for 'https://github.com/': No such device or address

Anyway, the output contains instructions to manually merge release/0.13.4 into master.

Originally posted by @github-actions in getsentry/publish#7613

Published successfully: run#23662543196

In the Publish using Craft step:

[info]  
[warn] Failed to merge release branch "release/0.13.4" into the target branch.
This is likely due to a merge conflict (e.g., in CHANGELOG.md).
All publish targets completed successfully — only the post-publish merge failed.

To resolve manually:
  1. Merge the release branch into the target branch, resolving conflicts
  2. Delete the release branch: git push origin --delete release/0.13.4

Error: fatal: could not read Username for 'https://github.com/': No such device or address

[success] Version 0.13.4 has been published!

#skip-changelog

[supervacuus]

Yeah, I see... There have been no changes in the change log since the release was triggered. So changes on master that would prevent auto-merges were not the cause here.

@BYK, do you have an explanation for why this failed?

This should definitely be merged, but I see that the new Validate PR workflow also failed. Maybe there is a connection between these new workflows and a central auth-related capability they depend on that still does not work (or just a missing new env or secret). Could imagine the same thing affected the publish run.