[pull] master from vuetifyjs:master

.github/CONTRIBUTING.md

@@ -1,23 +1,72 @@
 # Vuetify Contributing Guide
-Hello and thank you for your interest in helping make Vuetify better. Please take a few moments to review the following guidelines:
 
-## IMPORTANT INFORMATION
-* A detailed guide on how to [develop in Vuetify](https://vuetifyjs.com/getting-started/contributing/) is located in the documentation.
-* For general questions, please join [our Discord Community](https://community.vuetifyjs.com/).
+Thank you for your interest in improving Vuetify! Please review these guidelines to ensure a smooth contribution process.
+
+## Important Information
+
+- Detailed instructions for [Contributing to Vuetify](https://vuetifyjs.com/getting-started/contributing/) are available in the documentation.
+- For general questions, join [our Discord Community](https://community.vuetifyjs.com/).
 
 ## Reporting Issues
-* Issues **not** created with https://issues.vuetifyjs.com/ will be immediately closed.
-* The issue list of this repo is **exclusively** for Bug Reports and Feature Requests.
-* Bug reproductions should be as **concise** as possible.
-* **Search** for your issue, it _may_ have been answered.
-* See if the error is **reproduceable** with the latest version.
-* If reproduceable, please provide a [Codepen](https://template.vuetifyjs.com) or public repository that can be cloned to produce the expected behavior. It is preferred that you create an initial commit with no changes first, then another one that will cause the issue. 
-* **Never** comment "+1" or "me too!" on issues without leaving additional information, use the :+1: button in the top right instead.
+
+- Issues **must** be created using <https://issues.vuetifyjs.com/> or they will be closed immediately.
+- The issue list is **exclusively** for bug reports and feature requests.
+- Search for existing issues before submitting a new one.
+- Ensure the issue is reproducible with the [latest version](https://github.com/vuetifyjs/vuetify/releases/latest).
+- Provide a **minimal** and **concise** reproduction using [Vuetify Play](https://play.vuetifyjs.com/) or a public repository with:
+  - An initial commit showing the working state.
+  - A subsequent commit triggering the issue.
+- Include clear reproduction steps (actions another developer can follow after opening your link).
+- Avoid comments like "+1" or "me too!" without additional details—use the :+1: button instead.
 
 ## Pull Requests
-* Always work on a new branch. Making changes on your fork's `dev` or `master` branch can cause problems. (See [The beginner's guide to contributing to a GitHub project](https://akrabat.com/the-beginners-guide-to-contributing-to-a-github-project/))
-* Bug fixes should be submitted to the `master` branch.
-* New features and breaking changes should be submitted to the `dev` branch.
-* Use a descriptive title no more than 64 characters long. This will be used as the commit message when your PR is merged. 
-* For changes and feature requests, please include an example of what you are trying to solve and an example of the markup. It is preferred that you create an issue first however, as that will allow the team to review your proposal before you start. 
-* Please reference the issue # that the PR resolves, something like `Fixes #1234` or `Resolves #6458` (See [closing issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/))
+
+- Work on a new branch in your fork (e.g., `fix/1234-some-issue`), not `dev` or `master`.
+- Submit bug fixes to the `master` branch; new features or breaking changes to the `dev` branch.
+- Use a descriptive title (max 64 characters) for the PR—it will become the commit message.
+- Include examples of the problem and proposed solution, ideally referencing an existing issue (e.g., `Fixes #1234`).
+- Follow [commit guidelines](#commit-guidelines) for all changes.
+
+## Local Development Setup
+
+1. **Prerequisites:**
+   - Git (>v2.20)
+   - Node.js (LTS)
+   - [pnpm](https://pnpm.io/)
+   - Additional tools may be needed for [node-gyp](https://github.com/nodejs/node-gyp#installation) on Windows.
+
+1. **Clone and Install:**
+
+   ```bash
+   git clone https://github.com/vuetifyjs/vuetify.git
+   cd vuetify
+   pnpm i
+   pnpm build vuetify
+   pnpm build api
+   ```
+
+1. **Development:**
+   - Run `pnpm dev` from the root to start a dev server at `localhost:8090` with `packages/vuetify/dev/Playground.vue`.
+   - Test changes in `Playground.vue` and include its contents in your PR.
+   - For documentation, run `pnpm dev docs` (after building Vuetify with `pnpm build:lib`) at `localhost:8095`.
+
+1. **Submitting Changes:**
+   - Fork the repository and add your fork as a remote:
+
+     ```bash
+     git remote add fork https://github.com/YOUR_USERNAME/vuetify.git
+     ```
+
+   - Choose the correct base branch:
+     - Bug fixes/Documentation: `master`
+     - New features: `dev`
+   - Push your branch and open a PR.
+
+## Commit Guidelines
+
+Follow the [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) standard:
+
+- Format: `<type>(scope): <subject>` (e.g., `fix(VSelect): resolve dropdown bug`) or `<type>: <subject>` (e.g., `docs: update contributing guide`).
+- Subject: Max 60 characters, imperative mood (e.g., "fix", not "fixed").
+- Body: Reference issues (e.g., `resolves #1234`), wrap at 72 characters, explain "what" and "why" (not "how").
+- Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`, `revert`.

.github/FUNDING.yml

@@ -1,6 +1,6 @@
 # These are supported funding model platforms
 
-github: [johnleider, KaelWD, MajesticPotatoe]
+github: [johnleider, KaelWD, MajesticPotatoe, yuwu9145]
 patreon: vuetify
 open_collective: vuetify
 ko_fi: # Replace with a single Ko-fi username

.github/actions/download-locales/action.yml

@@ -20,6 +20,16 @@ runs:
         push_translations: false
         export_only_approved: false
         crowdin_branch_name: ${{ inputs.crowdin-branch }}
+    - name: Download ja-JP
+      uses: crowdin/github-action@v1.19.0
+      with:
+        download_language: ja
+        config: crowdin.yml
+        upload_sources: false
+        download_translations: true
+        push_translations: false
+        export_only_approved: false
+        crowdin_branch_name: ${{ inputs.crowdin-branch }}
     - name: Download zh-CN
       uses: crowdin/github-action@v1.19.0
       with:

.github/actions/nightly-release/action.yml

@@ -35,7 +35,7 @@ runs:
         repository: ${{ inputs.checkout-repo }}
         ref: ${{ inputs.checkout-ref }}
         fetch-depth: 0
-    - uses: ./.github/actions/yarn-install
+    - uses: vuetifyjs/setup-action@master
     - run: >-
         node -e "
           const json = require('./lerna.json');
@@ -45,9 +45,9 @@ runs:
     - id: get-version
       run: echo "full-version=$(node -e "console.log(require('./lerna.json').version)")-${{ inputs.release-id }}" >> $GITHUB_OUTPUT
       shell: bash
-    - run: yarn lerna version ${{ steps.get-version.outputs.full-version }} --no-push --no-commit-hooks --force-publish --yes
+    - run: pnpm lerna version ${{ steps.get-version.outputs.full-version }} --no-push --no-commit-hooks --force-publish --yes
       shell: bash
-    - run: yarn conventional-changelog -p angular --outfile ./packages/vuetify/CHANGELOG.md -r 2
+    - run: pnpm conventional-changelog -p vuetify --outfile ./packages/vuetify/CHANGELOG.md -r 2
       shell: bash
     - run: >-
         node -e "fs.writeFileSync(
@@ -56,9 +56,9 @@ runs:
         )"
       shell: bash
       working-directory: ./packages/vuetify
-    - run: yarn lerna run build --scope @vuetify/nightly
+    - run: pnpm lerna run build --scope @vuetify/nightly
       shell: bash
-    - run: yarn lerna run build --scope @vuetify/api-generator
+    - run: pnpm lerna run build --scope @vuetify/api-generator
       shell: bash
     - name: NPM Release
       run: |

.github/issue-close-app.yml

@@ -9,5 +9,3 @@ exception:
   - "johnleider"
   - "KaelWD"
   - "MajesticPotatoe"
-  - "jacekkarczmarczyk"
-  - "nekosaur"