Repository navigation
chore(release): 0.5.0-beta.1 - #291
Merged
Merged
Conversation
0.4.1 was never tagged. Serial instruments are a feature large enough for a minor release, and the timeout_ms change, which fails a slow measurement on an unchanged configuration, rides along with it under Changed (breaking) instead of shipping in a patch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The next release becomes 0.5.0, starting with 0.5.0-beta.1, in place of 0.4.1. The 0.4.1 preparation in #288 was merged but never tagged, so no 0.4.1 exists anywhere.
Why a minor release
Serial instruments (#269 to #287) add a backend, the
visa asrlcommands, the[[asrl]]and[devices.serial]tables, and serial devices invisa list, the API andvisa scan. That is a feature of the size a minor release carries.The
timeout_mschange from #250 rides along with it. In 0.4.0, HiSLIP and SOCKET waited for a reply until the command was cancelled, and VISA waited 5 seconds. Now every operation stops at the device'stimeout_ms, so a measurement longer than that fails although the configuration has not changed. The 0.4.1 notes listed this under Fixed; it now heads the release under Changed (breaking). The entry no longer says "3000 ms unless set":timeout_msis required inconfig.toml, and 3000 ms is whatvisa addandvisa scan --addwrite.Why a beta first
0.3.0 and 0.4.0 also opened with a beta. Several release jobs have not run at this tree yet: the unit tests on macOS and linux-arm64, the serial round trip in the NativeAOT arm64 image, and
download-artifactv8.0.2. A beta tag runs all of them before a stable tag does. Thedebjob also runs on a beta tag, but there it skips the package, as a pre-release gets none; it builds its first packages at 0.5.0.What else changes
The unreleased Debian package entry joins the release section and says that a pre-release carries no package. The READMEs name 0.5.0-beta.1. The install guide's examples go back to 0.4.0, the newest stable release. The project versions in the lock files follow the new version.
The pull request install test of the Debian package read the version from
Directory.Build.props, so on a pre-release versionbuild-deb.shrefused it. It now builds the package for the release that version leads to,0.5.0here; the installedivicli --versionstill reports0.5.0-beta.1.