2028-01-01: Bump the deprecated API version to v2.3.0#218
2028-01-01: Bump the deprecated API version to v2.3.0#218EdSchouten wants to merge 1 commit intomainfrom
Conversation
|
|
Google's planned end of support for the Bazel 8 long-term support (LTS) is December 2027: https://bazel.build/release Please consider that companies may have maintenance branches where they rely on LTS versions. Especially the upgrade from Bazel 8 to 9 is a challenge since WORKSPACE support is removed in Bazel 9, and migrating to bzlmod introduces unnecessary risk on frozen maintenance branches where stability is critical. Therefore, @EdSchouten , would it make sense to keep the Buildbarn support of Bazel 8.x until Google's end of support? In other words, extending the date 2027-07-01 to 2028-01-01 (or perhaps 2028-02-01 to avoid breaking changes during the new year holiday period). |
|
Sure! Let's pick 2028-01-01. |
EdSchouten
changed the title
In #218 it was brought up that Bazel 8.x remains supported until 2028-01-01. Let's align the date at which we bump the deprecated API version to v2.3.0 with that.
Because we always interpret Command.arguments[0] according to the rules of REv2.3, we shouldn't announce support for REv2.2 or lower, even as part of the deprecated API version.
EdSchouten
force-pushed
the
eschouten/20270701-rev23
branch
from
1722b2b to
9f3fedf
Compare
|
Thanks @EdSchouten! |
2 participants
Because we always interpret Command.arguments[0] according to the rules of REv2.3, we shouldn't announce support for REv2.2 or lower, even as part of the deprecated API version.