-
Notifications
You must be signed in to change notification settings - Fork 12
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
Correctly sort ECRs when there are only two in the list #139
Conversation
SortByPublication had a bug where it was checking only one of the candidates' versions but not the other. If there are only two candidates to be sorted then one's version wasn't being examined so the sort ended up being based on publish date only, ignoring the version. Now we check both candidates' versions so version is always the primary sort key, even when there are only two candidates.
/kind bug |
Thanks @acnodal-tc for the PR. |
/assign |
/ok-to-test |
/lgtm |
LGTM label has been added. Git tree hash: fb739630a41f2f56c00423d5851610250d1f0149
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: roivaz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
SortByPublication had a bug where it was checking only one of the
candidates' versions but not the other. If there are only two
candidates to be sorted then one's version wasn't being examined so
the sort ended up being based on publish date only, ignoring the
version.
Now we check both candidates' versions so version is always the
primary sort key, even when there are only two candidates.