fix: upgrade sprig to v3.2.2

[wanghong230]

fix #6863

Signed-off-by: Hong Wang [email protected]

Tips:

• Maybe add you organization to USERS.md.
• Your PR needs to pass the required checks before it can be approved. If the check is not required (e.g. E2E tests) it does not need to pass
• Sign-off your commits to pass the DCO check: git commit --signoff.
• Run make pre-commit -B to fix codegen or lint problems.
• Say how how you tested your changes. If you changed the UI, attach screenshots.
• If changes were requested, and you've made them, then dismis the review to get it looked at again.
• You can ask for help!

[crenshaw-dev]

lgtm. Any idea whether this will solve the workflow.name problem mentioned in the issue?

[codecov]

Codecov Report

Merging #6876 (f94c45d) into master (53057a1) will decrease coverage by 0.06%.
The diff coverage is n/a.

❗ Current head f94c45d differs from pull request most recent head bb8047a. Consider uploading reports for the commit bb8047a to get more accurate results

@@            Coverage Diff             @@
##           master    #6876      +/-   ##
==========================================
- Coverage   48.70%   48.64%   -0.07%     
==========================================
  Files         265      265              
  Lines       19161    19161              
==========================================
- Hits         9332     9320      -12     
- Misses       8784     8792       +8     
- Partials     1045     1049       +4     

Impacted Files	Coverage Δ
cmd/argo/commands/get.go	58.30% <0.00%> (-2.05%)	⬇️
cmd/argoexec/commands/emissary.go	50.35% <0.00%> (-1.44%)	⬇️
workflow/controller/operator.go	70.97% <0.00%> (-0.24%)	⬇️
workflow/metrics/server.go	19.29% <0.00%> (+3.50%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53057a1...bb8047a. Read the comment docs.

[wanghong230]

lgtm. Any idea whether this will solve the workflow.name problem mentioned in the issue?

No, it won't. I am following up on that.