chore(deps): update dependencies to non-breaking versions

[Copilot]

Bumps all dependencies and devDependencies to the latest minor/patch release within each package's current major version. The ^ range operator is preserved as-is; vite (pinned exact) is updated in kind.

Dependencies

Package	Old	New
@element-plus/icons-vue	^2.1.0	^2.3.2
axios	^1.12.0	^1.13.6
braintree-web-drop-in	^1.36.1	^1.46.0
dayjs	^1.11.18	^1.11.20
element-plus	^2.3.3	^2.13.5
pinia	^2.0.36	^2.3.1
vue	^3.5.13	^3.5.30
vue-eslint-parser	^10.1.1	^10.4.0
vue-router	^4.5.0	^4.6.4

devDependencies

Package	Old	New
@hcaptcha/types	^1.0.3	^1.2.0
@rushstack/eslint-patch	^1.2.0	^1.16.1
@types/braintree-web-drop-in	^1.34.1	^1.39.4
@types/node	^18.14.2	^18.19.130
@types/validator	^13.7.15	^13.15.10
@types/youtube	^0.0.47	^0.1.2
@vitejs/plugin-vue	^5.2.1	^5.2.4
@vitejs/plugin-vue-jsx	^4.1.1	^4.2.0
@vue/eslint-config-typescript	^11.0.2	^11.0.3
@vue/tsconfig	^0.1.3	^0.9.0
eslint	^8.34.0	^8.57.1
eslint-plugin-import	^2.30.0	^2.32.0
eslint-plugin-vue	^9.9.0	^9.33.0
husky	^8.0.0	^8.0.3
pretty-quick	^3.1.3	^3.3.1
sass	^1.62.0	^1.98.0
typescript	^4.8.4	^4.9.5
vite	6.3.6	6.4.1
vite-plugin-pwa	^0.21.1	^0.21.2
vue-tsc	^1.6.5	^1.8.27

Packages where a newer major exists (pinia v3, vue-router v5, prettier v3, etc.) are intentionally held at their current major — those are separate breaking-change upgrades.

Original prompt

Update package.json to bump all dependencies and devDependencies to the latest available versions that do NOT change the major version (minor/patch updates only).

Requirements:

• Modify only package.json in the repository Longwater1234/WedemyClient on branch main.
• Update both "dependencies" and "devDependencies" entries.
• For each package, set the version string to the newest release that shares the same major version as the current entry (non-breaking updates). Preserve the leading caret (^) operator for packages that currently have it.
• Do not change any other fields in package.json (name, scripts, etc.).
• Do not add or modify any lockfiles.

Deliverables:

• A PR targeting main with the title: "chore(deps): update dependencies to non-breaking versions".
• The PR should contain only the updated package.json.
• In the PR description include a brief summary listing each package updated with old -> new versions.

Current package.json contents to update:

{
"name": "wedemyvite",
"version": "2.0.0",
"private": true,
"author": "Davis Tibbz",
"license": "MIT",
"homepage": "https://github.com/Longwater1234/WedemyClient",
"engines": {
"node": ">=20.x"
},
"repository": {
"type": "git",
"url": "https://github.com/Longwater1234/WedemyClient.git"
},
"bugs": {
"url": "https://github.com/Longwater1234/WedemyClient/issues"
},
"scripts": {
"dev": "cross-env --max_old_space_size=4096 vite",
"build": "rimraf dist && vite build",
"preview": "vite preview",
"type-check": "vue-tsc --noEmit",
"lint": "eslint src --ext .vue,.js,.jsx,.cjs,.mjs,.ts,.tsx,.cts,.mts --fix",
"pretty": "prettier --write src/",
"prepare": "husky install"
},
"dependencies": {
"@element-plus/icons-vue": "^2.1.0",
"@hcaptcha/vue3-hcaptcha": "^1.3.0",
"@techassi/vue-youtube-iframe": "^1.0.6",
"@vueuse/core": "^9.13.0",
"axios": "^1.12.0",
"braintree-web-drop-in": "^1.36.1",
"dayjs": "^1.11.18",
"element-plus": "^2.3.3",
"pinia": "^2.0.36",
"vue": "^3.5.13",
"vue-eslint-parser": "^10.1.1",
"vue-github-button": "^3.1.3",
"vue-router": "^4.5.0"
},
"devDependencies": {
"@hcaptcha/types": "^1.0.3",
"@rushstack/eslint-patch": "^1.2.0",
"@types/braintree-web-drop-in": "^1.34.1",
"@types/node": "^18.14.2",
"@types/validator": "^13.7.15",
"@types/youtube": "^0.0.47",
"@vitejs/plugin-vue": "^5.2.1",
"@vitejs/plugin-vue-jsx": "^4.1.1",
"@vue/eslint-config-prettier": "^7.1.0",
"@vue/eslint-config-typescript": "^11.0.2",
"@vue/tsconfig": "^0.1.3",
"cross-env": "^7.0.3",
"eslint": "^8.34.0",
"eslint-plugin-import": "^2.30.0",
"eslint-plugin-unused-imports": "^2.0.0",
"eslint-plugin-vue": "^9.9.0",
"husky": "^8.0.0",
"npm-run-all": "^4.1.5",
"prettier": "^2.8.8",
"pretty-quick": "^3.1.3",
"rimraf": "^3.0.2",
"sass": "^1.62.0",
"typescript": "^4.8.4",
"vite": "6.3.6",
"vite-plugin-eslint": "^1.8.1",
"vite-plugin-pwa": "^0.21.1",
"vue-tsc": "^1.6.5"
}
}

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: update this to non-breaking changes dependencies

Assistant: Do you mean one of these? Pick one (or tell me a different approach):

1. Update each dependency and devDependency to the newest release that does NOT change the major version (i.e., bump minor/patch only), and return the updated package.json (I can also open a PR if you want).
2. Change the semver ranges to disallow breaking (e.g., replace ^ with ~ to allow only patch upgrades) and return the modified package.json.
3. Both: set ranges to ~ and also bump each package to the latest non-major version.

Also confirm:

• Update both "dependencies" and "devDependencies"? (I assume yes.)
• If you want a PR created, say "open a PR" and provide the repo owner/repo (you already gave repo — I can open a PR if you confirm).

User: udpate both dependency and devDep and create a PR

Assistant: Got it — I can open the PR. Quick clarifying questions before I make changes:

1. Which update strategy do you want?

   • A) Bump each dependency and devDependency to the newest release that does NOT change the major version (update minor/patch only).
   • B) Change semver ranges to disallow breaking upgrades (replace ^ with ~ so only patch-level upgrades are allowed).
   • C) Both: change ranges to ~ and also bump each package to the latest non-major version.

2. Should I update only package.json, or also update/add the lockfile (package-lock.json / yarn.lock)? (I can commit the lockfile if you want — recommend yes.)

3. Which base branch should the PR target? (If you don’t specify, I will use main.)

4. PR title and description — I can generate a concise title like "chore(deps): update dependencies to non-breaking versions" and include a summary of changes. Any preferences?

Answer these and I’ll open the PR in Longwater1234/Wed...

This pull request was created from Copilot chat.

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Longwater1234]

LGTM