ops-toolkit 1.2.1 → 1.2.2

package/.env.example

@@ -1,6 +1,15 @@
 # Environment variables for ops-toolkit
 # Copy this file to .env and fill in your values
 
+# Publishing to npm
+# Get an automation token from: https://www.npmjs.com/settings/tokens
+NPM_TOKEN=your_npm_automation_token_here
+
+# GitHub releases (optional, for creating GitHub releases)
+# Get a personal access token from: https://github.com/settings/tokens
+# Required scopes: repo
+GITHUB_TOKEN=your_github_token_here
+
 # Debug mode
 DEBUG=false
 NODE_ENV=development

package/.release-it.json

@@ -13,11 +13,13 @@
   },
   "npm": {
     "publish": true,
-    "access": "public"
+    "access": "public",
+    "skipChecks": true
   },
   "hooks": {
     "before:init": ["bun run lint", "bun run typecheck"],
     "after:bump": ["bun run build"],
+    "before:release": "npm config set //registry.npmjs.org/:_authToken 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",
     "after:release": ["git push origin HEAD"]
   },
   "plugins": {

package/AGENTS.md

@@ -36,6 +36,9 @@ bun test             # Run all tests
 ### Git & Release
 
 ```bash
+bun run publish:patch        # Upgrade patch version and publish (e.g., 1.2.1 → 1.2.2)
+bun run publish:minor        # Upgrade minor version and publish (e.g., 1.2.1 → 1.3.0)
+bun run publish:major        # Upgrade major version and publish (e.g., 1.2.1 → 2.0.0)
 bun run release              # Create release with changelog
 bun run release:minor        # Minor version bump
 bun run release:major        # Major version bump
@@ -199,15 +202,16 @@ try {
 
 ## Quick Reference
 
-| Task             | Command             |
-| ---------------- | ------------------- |
-| Start dev server | `bun run dev`       |
-| Build project    | `bun run build`     |
-| Run tests        | `bun test`          |
-| Type check       | `bun run typecheck` |
-| Lint and fix     | `bun run lint:fix`  |
-| Format code      | `bun run format`    |
-| Debug            | F5 in VS Code       |
+| Task             | Command                 |
+| ---------------- | ----------------------- |
+| Start dev server | `bun run dev`           |
+| Build project    | `bun run build`         |
+| Run tests        | `bun test`              |
+| Type check       | `bun run typecheck`     |
+| Lint and fix     | `bun run lint:fix`      |
+| Format code      | `bun run format`        |
+| Publish to npm   | `bun run publish:patch` |
+| Debug            | F5 in VS Code           |
 
 ## OpenCode Custom Commands
 

package/CHANGELOG.md

@@ -1,3 +1,12 @@
+
+
+## [1.2.2](https://github.com/liangshaojie/ops-toolkit/compare/v1.2.1...v1.2.2) (2026-01-11)
+
+
+### Features
+
+* add optimized npm publish commands ([5e96ee6](https://github.com/liangshaojie/ops-toolkit/commit/5e96ee649f1aa0cb9c9200c3a918800003029c27))
+
 # Changelog
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
@@ -23,4 +32,4 @@ All notable changes to this project will be documented in this file. See [standa
 ### Documentation
 
 - add custom commands reference ([340cc12](https://github.com/username/ops-toolkit/commits/340cc12889d30b99a21334457e28e601a5fc2bb9))
-- add development guide with tips and tricks ([b8017af](https://github.com/username/ops-toolkit/commits/b8017affb22ff7448c897d47e4b3b57c548c80b1))
+- add development guide with tips and tricks ([b8017af](https://github.com/username/ops-toolkit/commits/b8017affb22ff7448c897d47e4b3b57c548c80b1))

package/docs/PUBLISH.md

@@ -0,0 +1,172 @@
+# Publishing to npm
+
+## Quick Start
+
+To publish a new version to npm, run one of the following commands:
+
+```bash
+# Patch version (bug fixes): 1.2.1 → 1.2.2
+bun run publish:patch
+
+# Minor version (new features): 1.2.1 → 1.3.0
+bun run publish:minor
+
+# Major version (breaking changes): 1.2.1 → 2.0.0
+bun run publish:major
+```
+
+## What Happens When You Publish
+
+The `publish:*` commands automatically:
+
+1. **Quality Checks**
+   - Run ESLint to check code quality
+   - Run TypeScript type checking
+
+2. **Version Bump**
+   - Increment version number in package.json
+   - Create git tag (e.g., v1.2.2)
+   - Create git commit with changelog
+
+3. **Build**
+   - Build the project
+   - Generate distribution files in `dist/`
+
+4. **Changelog**
+   - Update CHANGELOG.md with changes
+   - Based on git commit history
+
+5. **Publish**
+   - Publish package to npm registry
+   - Create GitHub release
+   - Push git tags and commits to remote
+
+## Prerequisites
+
+Before publishing, make sure:
+
+1. **Code is committed**
+   - All changes are committed to git
+   - Working directory is clean
+
+2. **Tests pass**
+
+   ```bash
+   bun test
+   ```
+
+3. **Build succeeds**
+
+   ```bash
+   bun run build
+   ```
+
+4. **You're logged in to npm**
+   ```bash
+   npm login
+   ```
+
+## Version Guidelines
+
+### Patch (bug fixes)
+
+```bash
+bun run publish:patch
+```
+
+Use for:
+
+- Bug fixes
+- Small improvements
+- Non-breaking changes
+- Documentation updates
+
+### Minor (new features)
+
+```bash
+bun run publish:minor
+```
+
+Use for:
+
+- New features
+- Backwards compatible changes
+- Adding functionality
+
+### Major (breaking changes)
+
+```bash
+bun run publish:major
+```
+
+Use for:
+
+- Breaking changes
+- API changes
+- Removing features
+
+## Troubleshooting
+
+### "Git working directory not clean"
+
+```bash
+# Commit your changes first
+git add .
+git commit -m "your commit message"
+```
+
+### "403 Forbidden - You cannot publish over previously published versions"
+
+This means the version already exists on npm. The publish commands will automatically bump the version, so you shouldn't see this error.
+
+### Build errors
+
+```bash
+# Check build output
+bun run build
+
+# Fix any errors, then try publishing again
+bun run publish:patch
+```
+
+## Manual Publishing
+
+If you need more control, you can use `release-it` directly:
+
+```bash
+# Interactive release
+npx release-it
+
+# Specific version
+npx release-it 1.2.5
+
+# Skip git operations
+npx release-it --no-git --no-github
+```
+
+## After Publishing
+
+Once published, users can install your package:
+
+```bash
+# Global installation
+npm install -g ops-toolkit
+
+# Or using bun
+bun install -g ops-toolkit
+
+# Run the CLI
+ops --help
+```
+
+## Configuration
+
+Publishing behavior is configured in `.release-it.json`:
+
+- **Git**: Automatic commits and tags
+- **NPM**: Automatic publishing to public registry
+- **GitHub**: Automatic releases
+- **Hooks**: Pre-publish checks and post-build actions
+- **Changelog**: Auto-generated from commit history
+
+For more details, see [release-it documentation](https://github.com/release-it/release-it).

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "ops-toolkit",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "A comprehensive DevOps CLI toolkit with terminal UI",
   "main": "dist/index.js",
   "bin": {
-    "ops": "./dist/bin/ops-toolkit.js",
-    "ops-toolkit": "./dist/bin/ops-toolkit.js"
+    "ops": "dist/bin/ops-toolkit.js",
+    "ops-toolkit": "dist/bin/ops-toolkit.js"
   },
   "scripts": {
     "dev": "bun --watch src/index.ts",
@@ -20,7 +20,10 @@
     "release": "standard-version",
     "release:minor": "standard-version --release-as minor",
     "release:major": "standard-version --release-as major",
-    "publish": "release-it"
+    "publish": "release-it",
+    "publish:patch": "release-it --increment=patch --ci",
+    "publish:minor": "release-it --increment=minor --ci",
+    "publish:major": "release-it --increment=major --ci"
   },
   "keywords": [
     "cli",
@@ -37,7 +40,7 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/liangshaojie/ops-toolkit.git"
+    "url": "git+https://github.com/liangshaojie/ops-toolkit.git"
   },
   "bugs": {
     "url": "https://github.com/liangshaojie/ops-toolkit/issues"