Skip to content

Conversation

@nitishfy
Copy link
Member

@nitishfy nitishfy commented Jun 2, 2025

Closes #23216

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

Signed-off-by: Nitish Kumar <[email protected]>
@nitishfy nitishfy requested review from a team as code owners June 2, 2025 05:55
@bunnyshell
Copy link

bunnyshell bot commented Jun 2, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@codecov
Copy link

codecov bot commented Jun 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.02%. Comparing base (fb40acd) to head (e4ac45a).
⚠️ Report is 416 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #23222      +/-   ##
==========================================
- Coverage   60.08%   60.02%   -0.06%     
==========================================
  Files         342      342              
  Lines       57845    57845              
==========================================
- Hits        34754    34720      -34     
- Misses      20327    20342      +15     
- Partials     2764     2783      +19     

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

@blakepettersson blakepettersson merged commit 81ac621 into argoproj:master Jun 2, 2025
28 checks passed
@corneliusroemer
Copy link
Contributor

This hasn't fixed the issue unfortunately, the link still goes to 2.14 here:

https://github.com/argoproj/argo-cd/releases/tag/v3.0.5

chansuke pushed a commit to chansuke/argo-cd that referenced this pull request Jun 4, 2025
@nitishfy nitishfy deleted the patch-1 branch June 4, 2025 11:33
dsuhinin pushed a commit to dsuhinin/argo-cd that referenced this pull request Jun 16, 2025
dsuhinin pushed a commit to dsuhinin/argo-cd that referenced this pull request Jun 16, 2025
enneitex pushed a commit to enneitex/argo-cd that referenced this pull request Aug 24, 2025
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.

Release notes post at wrong blog post (for v2.14 instead of 3.0)

4 participants