Repository navigation
chore: release 2.2.1 - #141
Merged
Merged
Conversation
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.
Summary
Version 2.2.1 (from 2.2.0) and its CHANGELOG section, built from the PRs merged since v2.2.0:
One more entry under Fixed comes with the 9.2.5 packages and was measured here: a node of
--hostthat does not answer is given up after 4 seconds instead of the TCP timeout of the system.Patch version: one fix and documentation, no new option.
Compared with the released 2.2.0
The binary of the v2.2.0 release and this build, on the same test cluster:
statusas Text, Json and Markdown, dry runs ofsnapandcleanon@all, selections with excluded ranges and pools, storage threshold at 10%,--vmidnot found, invalid label and timestamp format,--timeout=0--hostthat does not answer: 22.3 s with 2.2.0, 5.2 s with this buildsnapwith a hook and--keep=2, a duplicate snapshot name (Error in task: ... already used, exit code 1),statusas Json,clean --keep=0; test snapshots removedNot reproduced on the cluster: the refused request of #140 (it needs a token without
VM.Snapshot); covered by the 5 tests ofRefusedRequestTests.Checks
Directory.Build.props2.2.1;cv4pve-autosnap --versionprints2.2.1cv4pve-tools-publish.ymlextracts the## [2.2.1]section (release notes)dotnet format --verify-no-changes,dotnet build -c Release,dotnet test: 113 passedThe tag
v2.2.1(which starts the publish workflow) is not pushed.