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

chore: change release-please manifest to fix false major version bumps #723

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

ege0zcan
Copy link
Contributor

Description

Due to the empty commits we made last week, release please now tries to make a version bump on every subpackage.

By changing the inception commit of release-please I am aiming to fix the wrong release created by release please and have release please only release actually changed subpackages.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ege0zcan ege0zcan requested a review from a team as a code owner January 14, 2025 15:52
@@ -1,5 +1,5 @@
{
"bootstrap-sha": "30ec14a11a4f9544d6b36a0196097b4425670937",
"bootstrap-sha": "ea570718da2b32b552b4308de1b4b3c2ee444b2b",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what we will do with changes made before this commit that should be included in release changelog?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there are any, looking at the open release-pleae PR we have the following in the release notes and both of those commits come after the new bootstrap commit

Bug Fixes
make proxy nodejs only (#716) (37cf726)
Performance Improvements
dispose chat controller in chatController tests (#717) (b0e6b78)

@ege0zcan ege0zcan merged commit a291093 into main Jan 14, 2025
6 checks passed
@ege0zcan ege0zcan deleted the releasePleaseFix branch January 14, 2025 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants