chore(deps): update dependency minimark to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
minimark	^0.2.0 → ^1.0.0

---

Release Notes

farnabaz/minimark (minimark)

v1.0.0

Compare Source

Features

• attribute support, html format, yaml props (a2d7063)
• markdown table generation (1484201)
• pre: filename, highlight & meta on markdown generation (d7de9cd)

Bug Fixes

• component: better inline detection (cf069ef)
• component: if component has a text sibling, it is inline (d8470e6)
• component: if there is no text between components they are inline (24c408f)
• component: preserve prefix whitespaces in component content (139cba4)
• do not indent inline components (b2f64a8)
• escape HTML entities (7ace288)
• line-break: stringify markdown style (c68ddf8)
• nested component indent (dabf03c)
• pre: decode html entities in code blocks (9df41a4)
• task list detection (76668bf)
• type import (46231d4)
• typecheck (07a01f1)
• types check (6f80492)

---

Configuration

📅 Schedule: Branch creation - Between 06:00 AM and 09:59 AM, only on Monday ( * 6-9 * * 1 ) in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@6053

commit: 5dbd4b0

[howwohmm]

Looking at this dependency update, there are several important considerations for a major version bump from 0.x to 1.0:

• Breaking changes risk: This is a major version update that introduces new dependencies (entities and js-yaml), suggesting significant internal changes. The docs build should be thoroughly tested since minimark appears to be used for markdown processing in the documentation. Check if any minimark APIs used in the codebase have changed or been removed.

• Bundle size impact: The addition of two new dependencies (entities at ~12KB and js-yaml at ~80KB) will increase the bundle size. Consider running pnpm why entities and pnpm why js-yaml to understand the dependency chain and verify these additions are intentional rather than accidental transitive deps.

• Test coverage verification: Run the full test suite with special attention to any markdown processing, documentation generation, or content parsing functionality. If there are specific tests for minimark integration, those should be verified first before merging.

The change itself looks structurally correct, but the major version bump warrants careful testing before deployment to ensure the documentation pipeline continues working as expected.