Skip to content

Conversation

release-please[bot]
Copy link
Contributor

🤖 I have created a release beep boop

2.0.0-preview.16 (2025-03-20)

Bug Fixes

  • always serialize security schemes in components (3aac661)
  • always serialize security schemes in components (a765acf)

This PR was generated with Release Please. See documentation.

@MaggieKimani1
Copy link
Contributor

@baywet, @andrueastman any idea why there are duplicate changelog entries?
image

Copy link

@baywet
Copy link
Member

baywet commented Mar 20, 2025

That's because the GitHub UI adds a recap of the commit messages in the merge commit.
So you have the same message in the merge and the actual commit.

And release please doesn't do any deduplication of the messages.

We could:

  • edit the merge commits messages on an ongoing basis.
  • use squash merge
  • pr release please to add a deduplication mechanism

@MaggieKimani1 MaggieKimani1 enabled auto-merge March 20, 2025 16:07
@MaggieKimani1 MaggieKimani1 merged commit 5d99cc4 into main Mar 20, 2025
15 checks passed
@MaggieKimani1 MaggieKimani1 deleted the release-please--branches--main--components--Microsoft.OpenApi branch March 20, 2025 16:07
Copy link
Contributor Author

🤖 Created releases:

🌻

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.

2 participants