Skip to content

Conversation

@nitishfy
Copy link
Member

everytime a new release is cut, the release page points to the the v3.0 blog always. The official blog post link is alway going to vary hence it is better to point to the official blog post site than a specific blog (otherwise we'll have to change it everytime a new release is cut). The upgrading docs follow the same pattern too at line 88.
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 Title of the PR
  • 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: nitishfy <[email protected]>
@nitishfy nitishfy requested review from a team as code owners October 27, 2025 10:06
@bunnyshell
Copy link

bunnyshell bot commented Oct 27, 2025

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔵 /bns:start to start the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

@nitishfy nitishfy changed the title chagne blog post link chore: change blog post link for release Oct 27, 2025
@codecov
Copy link

codecov bot commented Oct 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (master@0d0cec6). Learn more about missing BASE report.

Additional details and impacted files
@@            Coverage Diff            @@
##             master   #25088   +/-   ##
=========================================
  Coverage          ?   62.25%           
=========================================
  Files             ?      351           
  Lines             ?    49213           
  Branches          ?        0           
=========================================
  Hits              ?    30639           
  Misses            ?    15651           
  Partials          ?     2923           

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

@nitishfy nitishfy requested a review from gdsoumya October 28, 2025 16:04
Copy link
Member

@ishitasequeira ishitasequeira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!!

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.

3 participants