dart-sdk/tools/VERSION

32 lines
891 B
Plaintext
Raw Normal View History

# This file is used by tools/utils.py to generate version strings.
# The numbers are changed as follows:
#
# * New release cycle has begun (i.e. stable release was just made):
# - increase MINOR by 1
# - set "PATCH 0"
# - set "PRERELEASE 0"
# - set "PRERELEASE_PATCH 0"
#
# * Doing a push-to-trunk from bleeding_edge:
# (The first push-to-trunk in the release cycle will set PRERELEASE to 0)
# - increase PRERELEASE by 1
# - set "PRERELEASE_PATCH 0"
#
# * Doing a cherry-pick to trunk:
# - increase PRERELEASE_PATCH by 1
#
# * Making a stable release (i.e. new stable branch):
# - set "PRERELEASE 0"
# - set "PRERELEASE_PATCH 0"
# The new stable release version will sort higher than the prereleases.
#
# * Making cherry-picks to stable channel
# - increase PATCH by 1
#
Rename be channel to main. **This change cannot easily be reverted**: After reverting this change, dart-ci-internal-release-bucket-breakglass must be broken by a member of Dart EngProd and gs://dart-archive/channels/main/raw/latest must be purged as well as gs://dartlang-api-docs/channels/main/latest.txt. This operation would risk our release security and it is strongly preferred if any problems can be fixed forward instead. This change will upload the main channel builds to the main directory in the dart-archive bucket instead of the be directory. The existing builds remain where they are and the last version on the be channel remains permanently frozen. The downstream uses already have forward compatibility for the new channel name. The Dart recipes respect the input channel name and output to the release location by that name. The api.dart.dev service will notice when the main channel pops into existence and switch api.dart.dev/be to become api.dart.dev/main. The setup-dart github action will likewise notice when the main channel starts existing. The main channel is not an officially supported product since the builds are not signed and tested and we don't advertise the existence of these builds to our users. Ideally nobody would be broken by this change since they shouldn't be using the main channel builds, but if they are, they will have to rename the channel in their download links. This change ensures that all the release branches and release channels have the same matching names, which simplifies our infrastructure and makes our releases easier to understand. Fixes: b/270022416 Change-Id: Ib47ae7d2ded5fe0d405b3f19c34981c38082a090 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/327940 Commit-Queue: Jonas Termansen <sortie@google.com> Reviewed-by: Alexander Thomas <athom@google.com>
2023-11-13 13:27:24 +00:00
CHANNEL main
MAJOR 3
MINOR 6
PATCH 0
PRERELEASE 0
PRERELEASE_PATCH 0