Update CONTRIBUTING.md

Author: yamcodes

CONTRIBUTING.md

@@ -76,42 +76,6 @@ This will let GitHub know the issues are linked, and automatically close them on
 
 It's ok to have multiple commits in a single PR, you don't need to rebase or force push for your changes as we will use `Squash and Merge` to squash the commits into one commit when merging.
 
-## 🧑‍🔧 Maintenance
-
-This section is for maintainers with write access, or if you want to maintain your own forks.
-
-<table><tr><td>
-
-#### Build Locally
-
-For this type of setup, the building and publishing process is done on your local machine. Make sure you have your local [`npm` logged in](http://npm.github.io/installation-setup-docs/installing/logging-in-and-out.html) before doing that.
-
-In `package.json`, we usually have:
-
-```json
-{
-  "scripts": {
-    "prepack": "bun run build"
-  }
-}
-```
-
-So whenever you run `npm publish`, it will make sure you have the latest change in the distribution.
-
-</td><td>
-
-#### Build on CI
-
-For complex projects that take long time to build, we might move the building and publishing process to CI. So it doesn't block your local workflow.
-
-They will be triggered by the `v` prefixed git tag added by `bumpp`. The action is usually defined under `.github/workflows/release.yml`
-
-> When maintaining your own fork, you might need to see `NPM_TOKEN` secret to your repository for it to publish the packages.
-
-</td></tr></table>
-
-Changelogs are always generated by GitHub Actions.
-
 ## 📖 References
 
 ### Lint