chore: bump gitops engine + remove IterateHierarchyv1

[pjiang-dev]

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).

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[pjiang-dev]

@andrii-korotkov The build is failing due to

#39 107.6 # github.com/argoproj/argo-cd/v3/controller/cache
Error: #39 107.6 controller/cache/cache.go:677:14: clusterInfo.IterateHierarchy undefined (type "github.com/argoproj/gitops-engine/pkg/cache".ClusterCache has no field or method IterateHierarchy)

I see you made a related PR to remove this IterateHierarchy in argoproj/gitops-engine#748

Is this something you're still working on ? As i have a gitops-engine change which now includes this change

[andrii-korotkov]

Sorry, I didn’t submit a follow-up pr yet. I think you should be able to resolve it by just running codegen.

…

On Thu, Jul 24, 2025 at 10:49 AM Peter Jiang ***@***.***> wrote: *pjiang-dev* left a comment (argoproj/argo-cd#23924) <#23924 (comment)> @andrii-korotkov <https://github.com/andrii-korotkov> The build is failing due to #39 107.6 # github.com/argoproj/argo-cd/v3/controller/cache Error: #39 107.6 controller/cache/cache.go:677:14: clusterInfo.IterateHierarchy undefined (type "github.com/argoproj/gitops-engine/pkg/cache".ClusterCache has no field or method IterateHierarchy) I see you made a related PR to remove this IterateHierarchy in argoproj/gitops-engine#748 <argoproj/gitops-engine#748> Is this something you're still working on ? As i have a gitops-engine change which now includes this change — Reply to this email directly, view it on GitHub <#23924 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2VCNV7U22GJX7QEYU24YL3KEMCJAVCNFSM6AAAAACCJPS7OCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGMZTEMJSGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pjiang-dev]

I'll include the change to remove IterateHierachyv1 and codegen in this PR then.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.19%. Comparing base (be2c243) to head (7d59394).
⚠️ Report is 789 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #23924      +/-   ##
==========================================
+ Coverage   60.16%   60.19%   +0.03%     
==========================================
  Files         346      346              
  Lines       59277    59268       -9     
==========================================
+ Hits        35663    35678      +15     
+ Misses      20755    20726      -29     
- Partials     2859     2864       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[crenshaw-dev]

Wanna go ahead and either delete the calling method or at least mark it as deprecated? There are no callers in Argo CD, and I really doubt anyone is using this method as library code.

[pjiang-dev]

yea lets just delete it then if there are no references