Skip to content

added 0.7.3#1774

Merged
ijonele merged 3 commits intomainfrom
docs-073
Nov 21, 2025
Merged

added 0.7.3#1774
ijonele merged 3 commits intomainfrom
docs-073

Conversation

@ijonele
Copy link
Collaborator

@ijonele ijonele commented Nov 21, 2025

  • Replaced the latest binary version with v0.7.3 across the docs
  • Added v0.7.3 upgrade instructions for Barra and Mainnet
  • Added a warning about re-generating addresses in network overviews and upgrade instructions.

@ijonele ijonele marked this pull request as ready for review November 21, 2025 10:33
@github-actions github-actions bot added the docs label Nov 21, 2025
@ijonele ijonele requested a review from a team as a code owner November 21, 2025 10:33
@vercel
Copy link

vercel bot commented Nov 21, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
warden-help-center Ignored Ignored Preview Nov 21, 2025 10:42am

@ijonele
Copy link
Collaborator Author

ijonele commented Nov 21, 2025

@jlehtimaki

  • Is the release date correct? November 19
  • Are these block heights correct? 745501 (mainnet), 1310001 (barra)

@ijonele ijonele requested a review from jlehtimaki November 21, 2025 10:34
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 21, 2025

📝 Walkthrough

Walkthrough

The PR updates docs to reference the v0.7.3 wardend binary: replaces v0.7.2 links with v0.7.3, adds v0.7.3 rows to Mainnet and Barra version histories, introduces v0.7.3 upgrade pages for Mainnet and Barra, and adds warnings that keys generated with v0.7.2 are invalid and must be rotated.

Changes

Cohort / File(s) Change Summary
Binary download link updates
docs/developer-docs/docs/learn/warden-networks.md, docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md, docs/developer-docs/docs/operate-a-node/barra-testnet/join-barra.md
Updated wardend binary download links and prerequisites from v0.7.2 → v0.7.3
Overview pages & version history
docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md, docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md
Added v0.7.3 rows to version history tables; inserted global warnings about v0.7.2 key invalidation; updated Binary section references to v0.7.3
New upgrade guides
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md, docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.3.md
Added v0.7.3 upgrade instructions (stop node, replace wardend binary) and warnings to regenerate keys if created with v0.7.2
Minor formatting / EOF fixes
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.md, docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.1.md
Removed diff artifact markers and ensured trailing newlines

Sequence Diagram(s)

sequenceDiagram
  participant Operator as Operator
  participant Node as Node (wardend)
  participant Filesystem as Filesystem
  rect `#E8F0FF`
    Note over Operator,Node: Upgrade to v0.7.3 (doc-described flow)
  end
  Operator->>Node: Stop wardend
  Node-->>Operator: Confirm stopped
  Operator->>Filesystem: Replace binary with wardend v0.7.3
  Filesystem-->>Operator: Binary updated
  Operator->>Node: Start wardend v0.7.3
  Node-->>Operator: Running v0.7.3
  rect `#FFF4E6`
    Note over Operator: If keys were generated with v0.7.2\n -> Generate new keys with v0.7.3+ and move funds
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Potential attention points:

  • Verify all v0.7.2 → v0.7.3 links and dates (Mainnet/Barra heights and links).
  • Confirm warning wording about v0.7.2 key invalidation is accurate and consistently placed.

Possibly related PRs

Suggested reviewers

  • jlehtimaki
  • jjheywood

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'added 0.7.3' is vague and generic; it references the version number but lacks specificity about what was added or changed. Consider a more descriptive title like 'Update documentation for v0.7.3 release' or 'Add v0.7.3 upgrade instructions and docs updates'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description check ✅ Passed The description clearly relates to the changeset, outlining the three main updates: binary version replacement, new upgrade instructions, and warning additions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs-073

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98db0aa and 03eb3c1.

📒 Files selected for processing (4)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.3.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.3.md
  • docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md
  • docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md

⚙️ CodeRabbit configuration file

**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Files:

  • docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (1)
docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md (1)

11-15: Past spelling issue appears resolved.

The previous review flagged a spelling error ("threre" → "there") on line 12. The current version shows the correct spelling "there", so this appears to have been addressed.

The warning block is well-formatted and clearly communicates the critical requirement to regenerate keys when upgrading from v0.7.2.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 4

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9f917d7 and 98db0aa.

📒 Files selected for processing (9)
  • docs/developer-docs/docs/learn/warden-networks.md (2 hunks)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/join-barra.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.1.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.3.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.md (1 hunks)
  • docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md

⚙️ CodeRabbit configuration file

**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Files:

  • docs/developer-docs/docs/operate-a-node/barra-testnet/join-barra.md
  • docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md
  • docs/developer-docs/docs/learn/warden-networks.md
  • docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.3.md
  • docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md
  • docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md
  • docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md
  • docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.md
  • docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.1.md
🪛 LanguageTool
docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.3.md

[grammar] ~12-~12: Ensure spelling is correct
Context: ...** or newer and move any existing funds threre. **Keys generated with v0.7.2 are not vali...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md

[grammar] ~21-~21: Ensure spelling is correct
Context: ...** or newer and move any existing funds threre. **Keys generated with v0.7.2 are not vali...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md

[grammar] ~22-~22: Ensure spelling is correct
Context: ...** or newer and move any existing funds threre. **Keys generated with v0.7.2 are not vali...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.3.md

[grammar] ~12-~12: Ensure spelling is correct
Context: ...** or newer and move any existing funds threre. **Keys generated with v0.7.2 are not vali...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (7)
docs/developer-docs/docs/operate-a-node/barra-testnet/upgrade/v0.7.1.md (1)

1-9: LGTM!

The trailing newline addition is a standard cleanup with no content changes. The upgrade instruction is clear and correct.

docs/developer-docs/docs/operate-a-node/mainnet/upgrade/v0.7.1.md (1)

1-9: LGTM!

Consistent with the Barra v0.7.1 page. The trailing newline cleanup is standard; content remains unchanged and correct.

docs/developer-docs/docs/learn/warden-networks.md (1)

18-18: LGTM!

Binary version links are correctly updated from v0.7.2 to v0.7.3 for both Mainnet and Barra testnet. Formatting is consistent and links are properly structured.

Also applies to: 63-63

docs/developer-docs/docs/operate-a-node/mainnet/join-mainnet.md (1)

30-30: LGTM!

Binary download link correctly updated to v0.7.3. The change is consistent with the PR-wide updates and maintains proper link formatting.

docs/developer-docs/docs/operate-a-node/mainnet/mainnet-overview.md (1)

13-18: LGTM!

The version history table is properly updated with v0.7.3, the Binary section correctly references the latest version, and the new Endpoints section provides clear, well-organized information with helpful guidance. The EVM recommendation and chain.json reference are valuable additions.

Also applies to: 26-28, 30-59

docs/developer-docs/docs/operate-a-node/barra-testnet/join-barra.md (1)

30-30: LGTM!

Binary download link correctly updated to v0.7.3, consistent with the mainnet and PR-wide updates.

docs/developer-docs/docs/operate-a-node/barra-testnet/barra-overview.md (1)

19-29: Version history and binary reference updates look good.

The v0.7.3 table entry is properly formatted and consistent with existing entries. The warning block clearly communicates the critical information about v0.7.2 key invalidation, and the binary section correctly references v0.7.3. All documentation sections (endpoints, chain ID, denomination, faucet) are present and comprehensive.

@ijonele ijonele merged commit c65b1ca into main Nov 21, 2025
11 checks passed
@ijonele ijonele deleted the docs-073 branch November 21, 2025 10:51
@coderabbitai coderabbitai bot mentioned this pull request Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments