-
Notifications
You must be signed in to change notification settings - Fork 66
Omit Node Info rendering for 4.18 and earlier #787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sdodson
wants to merge
1
commit into
openshift:main
Choose a base branch
from
sdodson:omit-node-info-4.18-and-earlier
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+36
−2
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
Does github.com/blang/semver/v4 ParseTolerant accept prerelease tags like4.18.0-0.nightly-2024-01-01-000000and4.18.0-0.ci-2024-01-01-000000as valid semantic versions?💡 Result:
Yes, github.com/blang/semver/v4's ParseTolerant function accepts version strings like 4.18.0-0.nightly-2024-01-01-000000 and 4.18.0-0.ci-2024-01-01-000000 as valid semantic versions [1][2]. ParseTolerant is designed to parse version strings that do not strictly adhere to the Semantic Versioning 2.0.0 specification by normalizing them—such as removing a "v" prefix or adding missing patch numbers—before passing them to the standard Parse function [2][3][4]. Because your example strings already contain valid major, minor, and patch components (4.18.0) followed by valid prerelease tags, they are compatible with the library's parsing logic [3][4]. While an issue in 2019 (Issue
#55) identified a regression where certain versions with prerelease tags were incorrectly rejected due to logic related to leading-zero removal, this was addressed in a subsequent pull request (PR#56) that was merged into the master branch [5][6]. Consequently, modern versions of the library correctly handle these formats [7][6].Citations:
🏁 Script executed:
Repository: openshift/release-controller
Length of output: 2865
🏁 Script executed:
Repository: openshift/release-controller
Length of output: 17493
🏁 Script executed:
Repository: openshift/release-controller
Length of output: 5452
Nightly/CI prerelease tags are still gated —
4.18.0-0.nightly-*and4.18.0-0.ci-*parse as semver, soReleaseTagHasCheapRpmdb()returnsfalsefor them and the node-image-info path stays disabled in both changelog/API callers. If nightly/CI releases should remain exempt, detect those tag classes before the semver minor check.🧰 Tools
🪛 golangci-lint (2.12.2)
[error] 189-189: QF1001: could apply De Morgan's law
(staticcheck)
🤖 Prompt for AI Agents