The example release PR updated the minor version. Is it possible to release patch version every time?

The first PR should just remove the word "SNAPSHOT" from the version and not change any numbers and the second one should update the number and add the word "SNAPSHOT", right? Or am I missing anything?

The first PR should just remove the word "SNAPSHOT" from the version and not change any numbers and the second one should update the number and add the word "SNAPSHOT", right? Or am I missing anything?

That's also my understanding.

Release please uses conventional commits to determine the correct semantic version of the next release: https://github.com/googleapis/release-please#how-should-i-write-my-commits

The two example PRs in the description were formed using fake feat: or fix: commits for testing, and they are for differnet components with unrelated version numbers. Release PRs remove the "SNAPSHOT" as expected, and can also increment the semantic version as appropriate based off conventional commits.

The second "snapshot" commit will always just do a patch increment and add "-SNAPSHOT" again. The version for the next release will be determined by the next "release" PR.

"release" PRs are constantly updated by the Release Please bot based off new commits to master.