doc: Add note about Python symlinks (PR 2362) to CHANGELOG.md for v9.1.0 #2783
Conversation
The PR for this change was merged without a prefixed name, such as "lib:" or "fix:". That means release-please didn't include it in the changelog for v9.1.0. This change did end up affecting users, though. (See issue 2713 and PR 2721). Therefore, I believe it should be noted in the CHANGELOG.md, so users can better understand the behavior they are seeing.
DeeDeeG
force-pushed
the
add-PR-2362-to-changelog
branch
from
458b42e to
23604c2
Compare
|
The present PR adds #2362 to the Changelog properly, whereas it has been missing. I would appreciate a merge, thank you for considering. For context: My PR #2362 was merged a while ago but never showed in the Changelog. I think it should be in the Changelog, especially since it broke the official Apple-blessed process for signing apps for macOS. Affected users should know which versions are affected by the change (back to 9.1.0). (Side note: The actual breakage is since fixed in #2721. Considering that fix is in |
|
Sorry to ping again, but can I please get this merged? (I feel bad about breaking people's stuff, the least anyone can do is document the breakage properly, by having the offending change in the CHANGELOG.) |
….0 (#2783) The PR for this change was merged without a prefixed name, such as "lib:" or "fix:". That means release-please didn't include it in the changelog for v9.1.0. This change did end up affecting users, though. (See issue 2713 and PR 2721). Therefore, I believe it should be noted in the CHANGELOG.md, so users can better understand the behavior they are seeing.
Checklist
Description of change
Add an entry for PR #2362 to the CHANGELOG.md for version 9.1.0.
(Details below...)
PR #2362 was merged without a prefixed name, such as "lib:" or "fix:". That means
release-pleasedidn't include it in the changelog for v9.1.0.This change did end up affecting users, though. (See issue #2713 and PR #2721). Therefore, I believe PR #2362 should be noted in the CHANGELOG.md, so users can better understand the behavior they are seeing.
(And of course, I think a fix for the unintended side-effects of #2362 should be merged soon if reasonably possible. See: #2721 for a fix.)