Copier update (bump nuxt)

[ejfine]

Pull in upstream changes

[coderabbitai]

Warning

Rate limit exceeded

@ejfine has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 25 minutes and 40 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8b8d541 and f41f44e.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (9)

• .copier-answers.yml (1 hunks)
• .devcontainer/devcontainer.json (2 hunks)
• .devcontainer/install-ci-tooling.py (1 hunks)
• .pre-commit-config.yaml (2 hunks)
• extensions/context.py (2 hunks)
• pyproject.toml (1 hunks)
• template/.devcontainer/devcontainer.json.jinja (1 hunks)
• template/.pre-commit-config.yaml.jinja (4 hunks)
• template/frontend/package.json.jinja (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-nuxt

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Pull Request Overview

This PR updates various dependencies and tooling versions by pulling in upstream changes from the copier base template. The changes primarily involve version bumps for development tools, pre-commit hooks, VS Code extensions, and Node.js/Python packages.

• Bump various dependency versions including Nuxt, Vue, ESLint, and Python tooling
• Update pre-commit hook revisions and configurations
• Add new @types/node dependency to the frontend package template

Reviewed Changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
template/frontend/package.json.jinja	Adds @types/node dependency to frontend template
template/.pre-commit-config.yaml.jinja	Updates pre-commit hook revisions and simplifies pnpm commands
template/.devcontainer/devcontainer.json.jinja	Updates VS Code extension versions
pyproject.toml	Bumps pyright, copier, and copier-template-extensions versions
extensions/context.py	Updates numerous dependency versions in context variables
.pre-commit-config.yaml	Updates typos, hadolint, and ruff hook revisions
.devcontainer/install-ci-tooling.py	Updates tooling version constants
.devcontainer/devcontainer.json	Updates VS Code extension versions
.copier-answers.yml	Updates commit reference

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}