fix(ci): release site version check#2381
Open
universal-itengineer wants to merge 2 commits into
Open
Conversation
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
cd840ab to
0b7e8a7
Compare
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
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.
Description
Update the release-site version checker to read module versions from the module-specific page:
https://releases.deckhouse.io/modules/virtualization
The checker now parses editions from that page and validates the requested channel column there, instead of scraping separate edition pages (
/fe,/ee,/ce,/se-plus). The Taskfile description was updated to point to the same URL.This also aligns the
tools/moduleversionsGo directive with the workflow Go version:1.25.10.Why do we need it, and what problem does it solve?
The old parser depended on the HTML layout of edition pages and failed with
version not foundeven when the version was already published for the module. This caused false CI failures during release-channel validation.Using the module-specific page matches the data we need directly: one module, all editions, all release channels.
What is the expected result?
check:releasesshould pass when the requested module version is present on the module release page for the selected channel.Verified locally with:
go run ./main.go moduleversions --channel alpha --version v1.8.2 --attempt 1 --check-releases go test ./...Checklist
Changelog entries