From fc1a8e3aa92053ba348e8ef8955e34d82f04167c Mon Sep 17 00:00:00 2001
From: eouzoe <pappdatap@gmail.com>
Date: Tue, 14 Jul 2026 02:33:27 +0800
Subject: [PATCH] chore: remove version-update issue template

A contributor does not write and commit a report file for us to keep. Version
bumps are raised as a one-line PR with a description; the maintainer verifies
and merges. The template added noise, so it is removed.
---
 .github/ISSUE_TEMPLATE/version-update.md | 38 ------------------------
 1 file changed, 38 deletions(-)
 delete mode 100644 .github/ISSUE_TEMPLATE/version-update.md

diff --git a/.github/ISSUE_TEMPLATE/version-update.md b/.github/ISSUE_TEMPLATE/version-update.md
deleted file mode 100644
index 92c821b..0000000
--- a/.github/ISSUE_TEMPLATE/version-update.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-name: Version update report
-about: Report an outdated dependency or tool version (no code changes required)
-title: "chore(deps): bump <package> to <version>"
-labels: dependencies
-assignees: ""
----
-
-<!--
-  You do NOT need to install, build, or test anything.
-  Run `just check-versions` (or `just check-env`) and paste the output.
-  A maintainer applies the bump, syncs the lockfiles, runs the tests, and merges.
--->
-
-## Package
-
-<!-- exact npm identifier, e.g. @orpc/server — NOT the tool nickname -->
-
-- Package:
-- Kind: <!-- npm dependency / nixpkgs tool / devenv / other -->
-
-## Versions
-
-- **Project's current pinned version**: <!-- from bun.lock / flake.lock / devenv.yaml -->
-- **Latest version on official source**: <!-- e.g. 4.12.30 -->
-- **Source link**: <!-- official page you checked, e.g. https://www.npmjs.com/package/hono -->
-
-## Local environment check
-
-<!-- paste output of `just check-env` so maintainers know your toolchain state -->
-
-```text
-<paste `just check-env` output here>
-```
-
-## Notes
-
-<!-- Is this a major / breaking bump? Any risk you noticed? Anything the maintainer should watch? -->