Skip to content

[template-sync] Sync with nuxt-ui-templates/saas — 2026-04-06#131

Draft
github-actions[bot] wants to merge 1 commit intomainfrom
template-sync/2026-04-06-08552f764eb1b4bf
Draft

[template-sync] Sync with nuxt-ui-templates/saas — 2026-04-06#131
github-actions[bot] wants to merge 1 commit intomainfrom
template-sync/2026-04-06-08552f764eb1b4bf

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 6, 2026

Upstream changes since last sync: only a lock file maintenance update.

Compare: nuxt-ui-templates/saas@5132651...7b3f124


Changed files

File Action Reason
pnpm-lock.yaml Skipped Lock files are project-specific and auto-generated; no package.json changes accompanied this update

Summary

The only upstream change between the last synced commit (51326517) and the new HEAD (7b3f124) is a Renovate lock file maintenance PR (#272). It bumped internal resolution hashes for packages like @vue/compiler-sfc (3.5.30 → 3.5.31) and @babel/parser (7.29.0 → 7.29.2) in the upstream lock file — but made no changes to package.json.

Since pnpm-lock.yaml is regenerated from this project's own package.json and reflects this repo's dependency tree (which includes additional packages not in the template), applying the upstream lock file directly would be incorrect. This project's own Renovate bot will handle dependency updates independently.

No lint, typecheck, or build changes were needed — only the state file was updated.

Generated by Template sync ·

Upstream nuxt-ui-templates/saas had only a lock file maintenance update
(pnpm-lock.yaml) — no code or package.json changes to apply.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants