Open release 3.0.0 #6774
Open release 3.0.0 #6774
Conversation
|
Warning Rate limit exceeded@ausias-armesto has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 17 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis pull request includes several changes, primarily updating the version of the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.github/workflows/merge.yaml (1)
201-214: The Zulip notification integration looks good, with some suggestions for improvement.The notification step is well-integrated into the release process. Consider these enhancements:
- Move the Zulip organization URL to repository variables for better maintainability
- Use a more professional tone in the notification message
- Consider using a version-specific topic for better message organization
Apply this diff to implement the suggestions:
- name: Notify release uses: zulip/github-actions-zulip/send-message@v1 with: api-key: ${{ secrets.ZULIP_API_KEY }} email: ${{ secrets.ZULIP_EMAIL }} - organization-url: "https://hopr.zulipchat.com" + organization-url: ${{ vars.ZULIP_ORG_URL }} type: "stream" to: "Releases" - topic: "main" + topic: "v${{ steps.setup.outputs.current_version }}" content: | - I'm thrilled to inform the new hoprd version v${{ steps.setup.outputs.current_version }} has been released. + HOPR v${{ steps.setup.outputs.current_version }} has been released. [Release Notes](https://github.com/hoprnet/hoprnet/releases/tag/v${{ steps.setup.outputs.current_version }}) [Docker Hub](https://hub.docker.com/repository/docker/hoprnet/hoprd/tags)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.github/workflows/merge.yaml(1 hunks)Makefile(0 hunks)
💤 Files with no reviewable changes (1)
- Makefile
⏰ Context from checks skipped due to timeout of 90000ms (8)
- GitHub Check: hopli / docker
- GitHub Check: hoprd / docker
- GitHub Check: tests-smart-contracts
- GitHub Check: Docs / Rust docs
- GitHub Check: tests-smoke-websocket
- GitHub Check: tests-unit
- GitHub Check: Linter
- GitHub Check: tests-unit-nightly
The scope of this PR is to create the contents of the new release 3.0.0