Skip to content

fix: Fix Release Version #161

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.

Sign up for GitHub

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

Merged
holtskinner merged 2 commits into from
Jun 4, 2025
+4 −0
Merged

fix: Fix Release Version #161

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5e60ac
ci: Update PR template to clarify conventional commit syntax
holtskinner Jun 4, 2025
0f79606
Add context for release-please
holtskinner Jun 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@ Before submitting your PR, there are a few things you can do to make sure it goe

- [ ] Follow the [`CONTRIBUTING` Guide](https://github.com/google-a2a/a2a-python/blob/main/CONTRIBUTING.md).
- [ ] Make your Pull Request title in the <https://www.conventionalcommits.org/> specification.
- Important Prefixes for [release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a [SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking change (indicated by the `!`) and will result in a SemVer major.
- [ ] Ensure the tests and linter pass (Run `nox -s format` from the repository root to format)
- [ ] Appropriate docs were updated (if necessary)

Expand Down
Loading