On every startup, Arduino IDE checks for new versions of the IDE. If a newer version is available, a notification/dialog is shown offering an update.
"Newer" is determined by comparing the version of the user's IDE to the latest available version on the update channel. This comparison is done according to the Semantic Versioning Specification ("SemVer").
In order to facilitate beta testing, builds are generated of the Arduino IDE at the each stage in development. These builds are given an identifying version of the following form:
<version>-snapshot-<short hash> - builds generated for every push and pull request that modifies relevant files
<version>-nightly-<YYYYMMDD> - daily builds of the tip of the default branch
Change description
In order to cause these builds to be correctly considered "newer" than the release version, the version metadata must be bumped immediately following each release. This was not done for the 2.3.3 release.
The change proposed here will also serve as the metadata bump for the next release in the event that release is a minor release. In case it is instead a minor or major release, the version metadata will need to be updated once more before the release tag is created.
Motivation
On every startup, Arduino IDE checks for new versions of the IDE. If a newer version is available, a notification/dialog is shown offering an update.
"Newer" is determined by comparing the version of the user's IDE to the latest available version on the update channel. This comparison is done according to the Semantic Versioning Specification ("SemVer"). In order to facilitate beta testing, builds are generated of the Arduino IDE at the each stage in development. These builds are given an identifying version of the following form:
<version>-snapshot-<short hash>- builds generated for every push and pull request that modifies relevant files<version>-nightly-<YYYYMMDD>- daily builds of the tip of the default branchChange description
In order to cause these builds to be correctly considered "newer" than the release version, the version metadata must be bumped immediately following each release. This was not done for the 2.3.3 release.
The change proposed here will also serve as the metadata bump for the next release in the event that release is a minor release. In case it is instead a minor or major release, the version metadata will need to be updated once more before the release tag is created.
Other information
Fixes https://github.com/arduino/arduino-ide/issues/2538
Reference:
https://github.com/arduino/arduino-ide/blob/main/docs/internal/release-procedure.md#4-%EF%B8%8F-bump-version-metadata-of-packages
Related:
Reviewer checklist