Skip to content

chore: sync dev with main#1791

Closed
chip-peanut-bot[bot] wants to merge 20 commits intodevfrom
main
Closed

chore: sync dev with main#1791
chip-peanut-bot[bot] wants to merge 20 commits intodevfrom
main

Conversation

@chip-peanut-bot
Copy link
Copy Markdown
Contributor

Branch Sync

main is 6 commits ahead of dev.

Commits to sync:

• Update content submodule to latest main (18 commits)
• Merge pull request #1784 from peanutprotocol/auto/update-content-20260323-174045
• feat: add missing content routes, SEO footer, and verify-content script
• Merge pull request #1787 from peanutprotocol/feat/content-overhaul-main
• feat: add page count regression check to verify-content
• Merge pull request #1788 from peanutprotocol/fix/verify-page-count-regression


Auto-generated by Chip 🐿️

chip-peanut-bot bot and others added 6 commits March 23, 2026 17:40
…0323-174045

Update content submodule (18 commits)
Six content types had published content but no matching Next.js route —
they fell through to the catch-all recipient page. The validate-links
CI only checked against content directories, not actual routes.

New routes: use-cases, withdraw, stories, pricing, supported-networks.
ContentSEOFooter in marketing layout (below main footer).
verify-content.ts replaces validate-links.ts with 9 verification passes.
Content submodule bumped to include PRs #18-#21 (republish locales,
MDX upgrades, template fixes).
feat: content routes, SEO footer & verify-content script
Pass 10 tracks the number of published pages and errors if it drops.
Prevents accidental mass-unpublish like the 72-page incident from
commit 79cb1cd. Baseline stored in .verify-content-baseline (330 pages).

To intentionally lower the count:
  echo <new-count> > .verify-content-baseline
…gression

feat: page count regression guard in verify-content
<div className="flex flex-col gap-px overflow-hidden rounded-sm border border-n-1">
{stories.map((story) => (
<Link
key={story.slug}

Check failure

Code scanning / CodeQL

Stored cross-site scripting

Stored cross-site scripting vulnerability due to [stored value](1).
{stories.map((story) => (
<Link
key={story.slug}
href={`/${locale}/stories/${story.slug}`}

Check failure

Code scanning / CodeQL

Stored cross-site scripting

Stored cross-site scripting vulnerability due to [stored value](1).
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 24, 2026

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

Project Deployment Actions Updated (UTC)
peanut-wallet Ready Ready Preview, Comment Mar 27, 2026 9:24pm

Request Review

chip-peanut-bot bot and others added 3 commits March 25, 2026 09:55
Includes 6 newly published help articles + 4 stories with MDX.
…-content

chore: replace Notion FAQ link with help center + bump content
chip-peanut-bot bot and others added 6 commits March 25, 2026 11:27
/{locale} URLs (e.g. /en, /es-419, /pt-br) had no page and fell through
to the [...recipient] catch-all, resulting in 404s.

This broke breadcrumb "Home" links on all content/SEO pages since they
point to /{locale}.

Adds temporary (302) redirects for all 5 locale roots to /.
Non-permanent so we can replace with proper localized landing pages later.
The deposit route uses two URL prefixes:
- /deposit/from-{slug} for exchanges (entity data)
- /deposit/via-{slug} for rails/networks (DEPOSIT_RAILS)

verify-content.ts was mapping ALL deposit content to from-{slug},
so rail pages like via-sepa were never validated and broken links
to rail pages were not caught.

Changes:
- Hoist exchangeSlugs to module scope for reuse
- Route generation: exchanges get from-, non-exchange deposit content gets via-
- Published content check: same from-/via- logic in urlPattern
fix: redirect locale roots (/{locale}) to / to fix 404s
…urls

fix: verify-content handles from-/via- deposit URL prefixes
chip-peanut-bot bot and others added 2 commits March 25, 2026 11:54
Adds stories, use-cases, withdraw, supported-networks, and pricing
pages to the sitemap. Uses listPublishedSlugs() so new content
is automatically included on next build.

~40 published pages were missing from the sitemap.
chip-peanut-bot bot and others added 3 commits March 25, 2026 12:11
Fails CI if a published content type has routes but is missing from
sitemap.ts. Checks both content directories and singleton pages
(supported-networks, pricing).

Prevents the situation where new content types get published but
never appear in the sitemap for search engine indexing.
…rage

feat: verify-content Pass 11 — sitemap coverage check
@chip-peanut-bot
Copy link
Copy Markdown
Contributor Author

Superseded by new PR with conflicts resolved.

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.

2 participants