Skip to content

Conversation

@farnabaz
Copy link
Member

πŸ”— Linked issue

resolves #3426

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@vercel
Copy link

vercel bot commented Jun 24, 2025

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Updated (UTC)
content-docs βœ… Ready (Inspect) Visit Preview Jun 24, 2025 1:45pm

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jun 24, 2025

npm i https://pkg.pr.new/@nuxt/content@3427

commit: 58504dd

@cloudflare-workers-and-pages
Copy link

Deploying content with Β Cloudflare Pages Β Cloudflare Pages

Latest commit: 58504dd
Status:Β βœ…Β  Deploy successful!
Preview URL: https://1917f1cd.content-f0q.pages.dev
Branch Preview URL: https://fix-optional-markdown-option.content-f0q.pages.dev

View logs

@farnabaz farnabaz merged commit e2a0f69 into main Jun 25, 2025
6 checks passed
@farnabaz farnabaz deleted the fix/optional-markdown-option branch June 25, 2025 09:25
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.

Using build config make markdown mandatory to be set

2 participants