chore: [bot] release: 1.3.0#49
Conversation
Summary of ChangesHello @teutonet-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request marks the automated release of version 1.4.0 for the 'cluster-api-provider-hosted-control-plane'. It consolidates a significant number of new features and bug fixes, enhancing the provider's capabilities in areas such as security, observability, scalability, and overall stability. The changes aim to improve the management of hosted control planes, streamline operations, and ensure a more robust and feature-rich experience. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request, generated by a bot, prepares for the 1.4.0 release by updating the version in release-please/manifest.json and generating a new changelog entry. While the version bump is correct, the CHANGELOG.md file has a significant issue: the new section for version 1.4.0 incorrectly includes numerous changes from previous releases, leading to a bloated and confusing changelog. My review includes a comment on this issue, suggesting a review of the release-please configuration to fix the changelog generation process.
43d8bbf to
d8a571f
Compare
d8a571f to
e277e98
Compare
|
🤖 Created releases: 🌻 |
🤖 I have created a release *beep* *boop* --- ## [1.3.0](v1.2.2...v1.3.0) (2025-11-25) ### Features * add hash for kube-root-ca.crt configmap to konnectivity-agent ([#38](#38)) ([9f4e977](9f4e977)) * add nix dev-shell ([#51](#51)) ([d6c6eb1](d6c6eb1)) * auto-generate the metadata.yaml instead of manually adjusting it ([#42](#42)) ([4a29346](4a29346)) * update k8s dependencies + dependants ([#41](#41)) ([885dcb5](885dcb5)) ### Bug Fixes * always create new titleCaser ([#37](#37)) ([bafb5a1](bafb5a1)) * oidc jwks conformance ([#39](#39)) ([5925f36](5925f36)) * use correct namespace for dev ([#36](#36)) ([7f5e3f4](7f5e3f4)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
🤖 I have created a release beep boop
1.3.0 (2025-11-25)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.