Skip to content

chore(AIP-185): clarify in-place change language #1565

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
noahdietz merged 3 commits into from
Oct 6, 2025
+2 −2
Merged

chore(AIP-185): clarify in-place change language #1565

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
198c045
Correct one sentence in AIP-185
tlinkowski Oct 6, 2025
a518dc8
Apply reviewer's suggestion
tlinkowski Oct 6, 2025
8064235
Merge branch 'master' into patch-1
noahdietz Oct 6, 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: 2 additions & 2 deletions aip/general/0185.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,8 @@ Note: The use of the term "major version number" above is taken from
[semantic versioning][]. However, unlike in traditional semantic versioning,
Google APIs **must not** expose minor or patch version numbers. For
example, Google APIs use `v1`, not `v1.0`, `v1.1`, or `v1.4.2`. From a user's
perspective, major versions are updated in place, and users receive new
functionality without migration.
perspective, major versions are updated in place with minor/patch equivalent
changes, and users receive new functionality without migration.

A new major version of an API **must not** depend on a previous major version of
the same API. An API surface **must not** depend on other APIs, except for in
Expand Down