chore: add Knip to check for unused code and deps (#424)

* chore: added Knip

* Added back babel/runtime

* Added back babel/runtime as full dependency

* chore: fix merge conflict

Removed 'async' and 'didyoumean' dependencies, updated 'chalk' version.

* Update chalk dependency version to 5.6.2

---------

Co-authored-by: Leah Wasser <leah@pyopensci.org>

Author: JoshuaKGoldberg

.github/workflows/knip.yml

@@ -0,0 +1,25 @@
+name: Knip
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  knip:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@2028fbc5c25fe9cf00d9f06a71cc4710d4507903 # v6.0.0
+        with:
+          node-version: '22'
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Run Knip
+        run: npx knip

knip.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "https://unpkg.com/knip@5.71.0/schema.json",
+  "ignoreDependencies": ["@babel/runtime"],
+  "entry": [
+    "jest.config.js",
+    "src/**/__tests__/*",
+    "src/api.js",
+    "src/repo/*.js",
+    "src/util/*.js"
+  ],
+  "treatConfigHintsAsErrors": true
+}

other/MAINTAINING.md

@@ -59,22 +59,6 @@ feature. This keeps our git history clean, but more importantly, this allows us
 to make any necessary changes to the commit message so we release what we want
 to release. See the next section on Releases for more about that.
 
-## Release
-
-Our releases are automatic. They happen whenever code lands into `main`. A
-Circle CI build build gets kicked off and if it's successful, a tool called
-[`semantic-release`](https://github.com/semantic-release/semantic-release) is
-used to automatically publish a new release to npm as well as a changelog to
-GitHub. It is only able to determine the version and whether a release is
-necessary by the git commit messages. With this in mind, **please brush up on
-[the commit message convention][commit] which drives our releases.**
-
-> One important note about this: Please make sure that commit messages do NOT
-> contain the words "BREAKING CHANGE" in them unless we want to push a major
-> version. I've been burned by this more than once where someone will include
-> "BREAKING CHANGE: None" and it will end up releasing a new major version. Not
-> a huge deal honestly, but kind of annoying...
-
 ## Thanks!
 
 Thank you so much for helping to maintain this project!

package.json

@@ -15,6 +15,7 @@
   "scripts": {
     "add-contributor": "kcd-scripts contributors add",
     "build": "kcd-scripts build",
+    "knip": "knip",
     "lint": "eslint . && prettier --check --ignore-unknown .",
     "lint-fix": "eslint --fix . && prettier --write --ignore-unknown .",
     "test": "NODE_OPTIONS='--experimental-vm-modules' kcd-scripts test --watchAll=false",
@@ -46,9 +47,7 @@
   "homepage": "https://github.com/all-contributors/all-contributors-cli#readme",
   "dependencies": {
     "@babel/runtime": "^7.7.6",
-    "async": "^3.1.0",
-    "chalk": "^4.0.0",
-    "didyoumean": "^1.2.1",
+    "chalk": "^5.6.2",
     "inquirer": "^7.3.3",
     "json-fixer": "^1.6.8",
     "lodash": "^4.11.2",
@@ -58,19 +57,17 @@
   },
   "devDependencies": {
     "@eslint/js": "^9.39.2",
-    "cz-conventional-changelog": "^3.3.0",
     "eslint": "^9.39.2",
-    "eslint-config-prettier": "^10.1.8",
     "eslint-plugin-import": "^2.32.0",
     "eslint-plugin-jest": "^29.12.1",
     "git-cz": "^4.7.6",
-    "kcd-scripts": "^16.0.0",
     "globals": "^17.1.0",
     "husky": "^9.1.0",
+    "kcd-scripts": "^16.0.0",
+    "knip": "^5.83.1",
     "lint-staged": "^16.2.7",
     "nock": "^14.0.10",
-    "prettier": "^3.8.1",
-    "semantic-release": "^25.0.2"
+    "prettier": "^3.8.1"
   },
   "optionalDependencies": {
     "prettier": "^3"