Skip to content

fix(content): refresh Notro Discord file limits and accurate feature claims - #36

Draft
writingdeveloper wants to merge 1 commit into
mainfrom
fix/notro-landing-meta-20261013
Draft

writingdeveloper wants to merge 1 commit into
mainfrom
fix/notro-landing-meta-20261013

Conversation

@writingdeveloper

@writingdeveloper writingdeveloper commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Update only Notro EN/KO portfolio description, reflecting Discord's Aug 2026 free 20MB cap, attachment-based emoji (not native Nitro), no client mods/tokens, and unsigned installer. Existing local portfolio worktrees and uncommitted files were not modified.

CI findings (Oct 13, 2026): content tests, type checks, lint, translation parity, and production build pass. The existing dependency audit blocks the PR: npm audit --audit-level=high reports 11 vulnerabilities (10 high, 1 critical) involving Next.js, sharp, braces, brace-expansion, and source-map-js. Separate portfolio dependency/security work is already in progress; don't bypass audit or merge until addressed/revalidated. This PR does not change dependencies. See https://github.com/writingdeveloper/portfolio/actions/runs/38486167720.

Related Notro PR: writingdeveloper/Notro#1 (CI green). Production writingdeveloper.blog/projects/notro still requires merge and deployment; no claim of live site change.

@vercel

vercel Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
portfolio Ready Ready Preview Oct 13, 2026 11:46pm UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — e376da56 Deployed Oct 13, 2026 by vercel[bot]
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