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

The current tag v2.5.1 is from May 2022 #562

Closed
andrii-korotkov opened this issue Jun 11, 2024 · 2 comments
Closed

The current tag v2.5.1 is from May 2022 #562

andrii-korotkov opened this issue Jun 11, 2024 · 2 comments
Labels
solution/wontfix This will not be worked on

Comments

@andrii-korotkov
Copy link

Hello,
I hope your day is going well.
I’ve noticed that the current tag is more than two years old. I wonder how easy it is to release a new one to be used by other projects. I understand that there may have not been much work on this, but there were still some contributions.
Thanks.

@andrii-korotkov
Copy link
Author

andrii-korotkov commented Jun 11, 2024

Answered here argoproj/gitops-engine#584 (comment)

We currently just point Argo CD at a certain commit on the master branch.

@andrii-korotkov andrii-korotkov closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
@agilgur5
Copy link
Member

agilgur5 commented Jun 11, 2024

And here: #453 (comment)

CD and Workflows both use a SHA directly as this repo has no release process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution/wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants