build(deps): downgrade argoproj/argo-cd
to v2.8.1
#354
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.
TLDR: This PR downgrades
argoproj/argocd
tov2.8.1
to unblock our releases whilst still 🤞 ensuring that the functionality added in #337 still works.Our release build is currently broken. I had hoped that bumping versions (#347) in the GitHub action would fix this, but it turns out that this is due to an issue in the version of
argoproj/argo-cd
that we currently reference.Goreleaser log (
v2.8.3
):The bug in
argo-proj/argocd
was introduced in argoproj/argo-cd#14979, which (per this comment) was first released inv2.8.2
. We currently referencev2.8.3
which was introduced as part of #337 (added support for application set sync policies).Initially, I thought we may as well upgrade to the latest version of
argoproj/argocd
as this would address #326 at the same time. However, unfortunately, the issue still exists withv2.9.1
. Goreleaser log (v2.8.3
):Hence.... Downgrading for now... As soon as I get the chance, I will try to put a fix through to
argoproj/argocd
.