Skip to content

V3.0.0#702

Merged
mjadach-iv merged 6 commits intomainfrom
V3.0.0
Aug 11, 2025
Merged

V3.0.0#702
mjadach-iv merged 6 commits intomainfrom
V3.0.0

Conversation

@mjadach-iv
Copy link
Contributor

@mjadach-iv mjadach-iv commented Aug 11, 2025

Summary by CodeRabbit

  • New Features

    • Export strategies to YAML from the Configuration page with improved formatting and per-address filenames.
    • Info page revamp: clearer connectivity status with tooltip, refined sync display, added Hopr/Blockchain network rows, and explicit “Faulty RPC” indicator when channels are corrupted.
    • Corrupted channels are now fetched and surfaced during login and info refresh.
  • Chores

    • Updated Node.js targets (build: 22.x/24.x; release/Docker: 22.x).
    • Disabled scoped registry overrides to use the default registry.
    • Upgraded Hopr SDK to 3.0.1.

@coderabbitai
Copy link

coderabbitai bot commented Aug 11, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Updates CI and Docker Node.js versions, disables @hoprnet scoped registries, bumps @hoprnet/hopr-sdk to 3.0.1, adds corrupted-channels fetch/state and thunk, integrates corrupted channels into login/init and info flows, and adds strategies YAML export in configuration UI.

Changes

Cohort / File(s) Summary
CI Node versions
/.github/workflows/build.yaml, /.github/workflows/release.yaml
Build matrix changed from [20.x, 22.x] to [22.x, 24.x]; release workflow now pins node-version: 22.x instead of using a variable.
Docker build base
/Dockerfile
Build/deps stages base image bumped from node:20-bullseye-slim to node:22-bullseye-slim; runtime nginx stage unchanged.
Registry config
.npmrc, .yarnrc
Commented out @hoprnet scoped registry entries so the scope falls back to the default npm registry.
Dependency bump
package.json
Updated @hoprnet/hopr-sdk from a pre-release (3.0.0-pr...) to 3.0.1.
Login/init flow
src/components/ConnectNode/modal.tsx, src/router.tsx
Added dispatches of getChannelsCorruptedThunk during node login and URL-init flows (after channels fetch).
Info page data/UI
src/pages/node/info/index.tsx
Fetches corrupted channels; adds channelsCorrupted derived state; updates connectivity/sync/provider/network rows and renders faulty provider when corrupted channels present.
Strategies export
src/pages/node/configuration.tsx
Reworked YAML generation for strategies, added exportToFile-based export button; filename includes node address.
Redux slice additions
src/store/slices/node/actionsAsync.ts, src/store/slices/node/initialState.ts
New thunk getChannelsCorruptedThunk (with pending/fulfilled/rejected cases) and new channels.corrupted initial state; refactored getChannelsThunk fulfillment to use a local channels variable and updated parsing logic.

Sequence Diagram(s)

sequenceDiagram
  actor User
  participant UI as ConnectNode/Router
  participant Store as Redux Store
  participant SDK as HOPR SDK API

  User->>UI: Initiate login / URL init
  UI->>Store: dispatch(getAddressesThunk)
  Store->>SDK: getAddresses
  SDK-->>Store: addresses
  Store-->>UI: addresses stored

  UI->>Store: dispatch(getChannelsThunk)
  Store->>SDK: getChannels
  SDK-->>Store: channels
  Store-->>UI: channels stored

  UI->>Store: dispatch(getChannelsCorruptedThunk)
  Store->>SDK: getChannelsCorrupted
  SDK-->>Store: { channelIds }
  Store-->>UI: corrupted channels stored

  UI->>Store: dispatch(getConfigurationThunk)
  Store->>SDK: getConfiguration
  SDK-->>Store: configuration
  Store-->>UI: configuration stored
Loading
sequenceDiagram
  participant Info as Info Page
  participant Store as Redux Store
  participant SDK as HOPR SDK API

  Info->>Store: dispatch(getChannelsCorruptedThunk)
  Store->>SDK: getChannelsCorrupted
  SDK-->>Store: { channelIds }
  Store-->>Info: update channelsCorrupted
  Info->>Info: Render provider as faulty if channelsCorrupted
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested labels

devops

Suggested reviewers

  • esterlus
  • Jaguaras

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2684c14 and e0b51d9.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (12)
  • .github/workflows/build.yaml (1 hunks)
  • .github/workflows/release.yaml (1 hunks)
  • .npmrc (1 hunks)
  • .yarnrc (1 hunks)
  • Dockerfile (2 hunks)
  • package.json (1 hunks)
  • src/components/ConnectNode/modal.tsx (1 hunks)
  • src/pages/node/configuration.tsx (6 hunks)
  • src/pages/node/info/index.tsx (5 hunks)
  • src/router.tsx (1 hunks)
  • src/store/slices/node/actionsAsync.ts (7 hunks)
  • src/store/slices/node/initialState.ts (2 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch V3.0.0

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@mjadach-iv mjadach-iv merged commit 4e856a7 into main Aug 11, 2025
3 checks passed
@mjadach-iv mjadach-iv deleted the V3.0.0 branch August 11, 2025 09:03
This was referenced Sep 11, 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.

1 participant