Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: change what latest chart actually means #128

Merged
merged 1 commit into from
Sep 18, 2024
Merged

fix: change what latest chart actually means #128

merged 1 commit into from
Sep 18, 2024

Conversation

colesnodgrass
Copy link
Member

  • prior to this change the most recently published chart was always considered the latest chart
  • now the latest chart will be the most recent chart that does not contain any sort of modifier after the release version
    • e.g. given the latest releases of 1.0.0-beta-hash, 1.0.0-alpha, 0.463.124, the latest version would be 0.463.124

@colesnodgrass colesnodgrass requested a review from a team as a code owner September 18, 2024 23:05
@colesnodgrass colesnodgrass merged commit 00ab459 into main Sep 18, 2024
2 checks passed
@colesnodgrass colesnodgrass deleted the cole/fix-latest-check branch September 18, 2024 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bgroff bgroff bgroff approved these changes

@perangel perangel perangel approved these changes

@abuchanan-airbyte abuchanan-airbyte Awaiting requested review from abuchanan-airbyte

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@colesnodgrass @perangel @bgroff