Skip to content

WIP feat(gnoland1): cherry-pick client updates from master#5298

Open
moul wants to merge 1 commit intochain/gnoland1from
gnoland1-clients-updates
Open

WIP feat(gnoland1): cherry-pick client updates from master#5298
moul wants to merge 1 commit intochain/gnoland1from
gnoland1-clients-updates

Conversation

@moul
Copy link
Member

@moul moul commented Mar 16, 2026

Cherry-picks from master:

These are client-side changes (gnoweb/docs) that don't affect consensus.

Related: #5296

@Gno2D2
Copy link
Collaborator

Gno2D2 commented Mar 16, 2026

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):
  • IGNORE the bot requirements for this PR (force green CI check)
Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

No automated checks match this pull request.

☑️ Contributor Actions:
  1. Fix any issues flagged by automated checks.
  2. Follow the Contributor Checklist to ensure your PR is ready for review.
    • Add new tests, or document why they are unnecessary.
    • Provide clear examples/screenshots, if necessary.
    • Update documentation, if required.
    • Ensure no breaking changes, or include BREAKING CHANGE notes.
    • Link related issues/PRs, where applicable.
☑️ Reviewer Actions:
  1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.
📚 Resources:
Debug
Manual Checks
**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

  • Any user with comment edit permission

@codecov
Copy link

codecov bot commented Mar 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@moul moul changed the title chore(gnoland1): cherry-pick client updates from master WIP feat(gnoland1): cherry-pick client updates from master Mar 16, 2026
@moul moul mentioned this pull request Mar 16, 2026
7 tasks
@ajnavarro
Copy link
Contributor

I think you need to run make generate too.

@moul moul force-pushed the chain/gnoland1 branch 2 times, most recently from 4e73f6d to 2cf2b79 Compare March 16, 2026 16:15
Add the legal notice required by the legal team to the gnoweb footer,
with links to three legal documents (Gno GPL License, Network
Interaction Terms, and Contributor License Agreement). Also add
`TERMS.md` and` CLA.md` at the repo root with the full legal text
provided by counsel.

**Footer (gnoweb):**

- Replace the former "Legal" section (_Terms_ + _Privacy_ pointing to
the same `LICENSE.md`) with a proper legal notice paragraph and three
named legal document links (Gno GPL License, Network Interaction Terms,
Contributor License Agreement)
- Restructure the footer layout into two zones: navigation + social
links on top, full-width legal disclaimer below
- Navigation links now sit inline with the logo (`.nav-primary, 7 grid
columns`), social links occupy the right column (.`nav-social, 3 grid
columns`)

**Legal documents:**

- `TERMS.md`: Gno.land Network Interaction Terms (sections covering
content ownership, on-chain licensing, disclaimers, etc.)
- `CLA.md `: Gno.land Contributor License Agreement (sections covering
copyright/patent grants, contributor representations, CLA Hash
mechanism, etc.)

<img width="1782" height="230" alt="Capture d’écran 2026-02-20 à 11 47
27"
src="https://github.com/user-attachments/assets/a6276e7e-ef13-41f9-afce-2f0fde66693e"
/>

---------

Co-authored-by: Jae Kwon <53785+jaekwon@users.noreply.github.com>
Co-authored-by: jaekwon <jae@tendermint.com>
@moul moul force-pushed the gnoland1-clients-updates branch from 939ee22 to e32f291 Compare March 16, 2026 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🐳 devops 🌍 gnoweb Issues & PRs related to gnoweb and render 📦 ⛰️ gno.land Issues or PRs gno.land package related 📄 top-level-md

Projects

Status: In Progress
Status: 📥 Inbox

Development

Successfully merging this pull request may close these issues.

4 participants