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.

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

chore(repo-server): unify semver resolution in new versions subpackage #20216

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

PaulSonOfLars
Copy link
Contributor

Unify semver resolution across helm/OCI/git into a single package, to ensure we don't end up with mismatched logic for different services

Follow up to #20096, as requested here. cc @blakepettersson

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@PaulSonOfLars PaulSonOfLars requested a review from a team as a code owner October 3, 2024 17:17
Copy link

bunnyshell bot commented Oct 3, 2024

✅ Preview Environment deployed on Bunnyshell

Component Endpoints
argocd https://argocd-4ej5vm.bunnyenv.com/
argocd-ttyd https://argocd-web-cli-4ej5vm.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔴 /bns:stop to stop the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

Copy link

bunnyshell bot commented Oct 3, 2024

✅ Preview Environment created on Bunnyshell but will not be auto-deployed

See: Environment Details

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

Copy link
Member

@blakepettersson blakepettersson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking good so far! Just a few minor comments

util/helm/client.go Outdated Show resolved Hide resolved
util/versions/version.go Show resolved Hide resolved
@blakepettersson
Copy link
Member

I think you also need to run make mockgen

@blakepettersson blakepettersson changed the title fix: Unify semver resolution in new versions subpackage fix: unify semver resolution in new versions subpackage Oct 4, 2024
@blakepettersson blakepettersson changed the title fix: unify semver resolution in new versions subpackage refactor(repo-server): unify semver resolution in new versions subpackage Oct 4, 2024
@blakepettersson blakepettersson changed the title refactor(repo-server): unify semver resolution in new versions subpackage chore(repo-server): unify semver resolution in new versions subpackage Oct 4, 2024
Signed-off-by: Paul Larsen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants