ci(release): migrating from standard-version to release-please

standard-version is deprecated. Release Please is the recommended tool as a replacement.

closes #113

Author: Tiberriver256

.github/release-please-config.json

@@ -0,0 +1,14 @@
+{
+  "packages": {
+    ".": {
+      "release-type": "node",
+      "package-name": "@tiberriver256/mcp-server-azure-devops",
+      "changelog-path": "CHANGELOG.md",
+      "bump-minor-pre-major": true,
+      "bump-patch-for-minor-pre-major": true,
+      "draft": false,
+      "prerelease": false
+    }
+  },
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
+} 

.github/release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.11"
+} 

.github/workflows/release-please.yml

@@ -0,0 +1,49 @@
+name: Release Please
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: google-github-actions/release-please-action@v4
+        id: release
+        with:
+          token: ${{ secrets.RELEASE_PAT }}
+          config-file: .github/release-please-config.json
+          manifest-file: .github/release-please-manifest.json
+          
+      # The following steps only run if a new release is created
+      - name: Checkout code
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actions/checkout@v3
+        with:
+          ref: ${{ steps.release.outputs.tag_name }}
+          
+      - name: Setup Node.js
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: 'lts/*'
+          registry-url: 'https://registry.npmjs.org/'
+          
+      - name: Install Dependencies
+        if: ${{ steps.release.outputs.release_created }}
+        run: npm ci
+        
+      - name: Build package
+        if: ${{ steps.release.outputs.release_created }}
+        run: npm run build
+        
+      - name: Publish to npm
+        if: ${{ steps.release.outputs.release_created }}
+        run: npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} 

.github/workflows/release.yml

@@ -131,18 +131,27 @@ npm run commit
 
 ## Automated Release Workflow
 
-Our project uses an automated release workflow that leverages Conventional Commits to manage semantic versioning, generate changelogs, and create GitHub Releases.
-
-The workflow is currently triggered manually via GitHub Actions' `workflow_dispatch` feature. In the future, it may be configured to run automatically on merges to the `main` branch.
-
-When the workflow runs, it:
-
-1. Analyzes the commit messages since the last release
-2. Determines the appropriate semantic version bump
-3. Updates the version in package.json
-4. Generates or updates the CHANGELOG.md file
-5. Creates a new Git tag
-6. Creates a GitHub Release with release notes
+Our project uses [Release Please](https://github.com/googleapis/release-please) to automate releases based on Conventional Commits. This approach manages semantic versioning, changelog generation, and GitHub Releases creation.
+
+The workflow is automatically triggered on pushes to the `main` branch and follows this process:
+
+1. Release Please analyzes commit messages since the last release
+2. If releasable changes are detected, it creates or updates a Release PR
+3. When the Release PR is merged, it:
+   - Updates the version in package.json
+   - Updates CHANGELOG.md with details of all changes
+   - Creates a Git tag and GitHub Release
+   - Publishes the package to npm
+
+### Release PR Process
+
+1. When commits with conventional commit messages are pushed to `main`, Release Please automatically creates a Release PR
+2. The Release PR contains all the changes since the last release with proper version bump based on commit types:
+   - `feat:` commits trigger a minor version bump
+   - `fix:` commits trigger a patch version bump
+   - `feat!:` or `fix!:` commits with breaking changes trigger a major version bump
+3. Review the Release PR to ensure the changelog and version bump are correct
+4. Merge the Release PR to trigger the actual release
 
 This automation ensures consistent and well-documented releases that accurately reflect the changes made since the previous release.
 

CONTRIBUTING.md

@@ -18,6 +18,17 @@
       "path": "./node_modules/cz-conventional-changelog"
     }
   },
+  "release-please": {
+    "release-type": "node",
+    "changelog-types": [
+      {"type": "feat", "section": "Features", "hidden": false},
+      {"type": "fix", "section": "Bug Fixes", "hidden": false},
+      {"type": "chore", "section": "Miscellaneous", "hidden": false},
+      {"type": "docs", "section": "Documentation", "hidden": false},
+      {"type": "perf", "section": "Performance Improvements", "hidden": false},
+      {"type": "refactor", "section": "Code Refactoring", "hidden": false}
+    ]
+  },
   "scripts": {
     "build": "tsc && chmod +x dist/index.js",
     "dev": "ts-node-dev --respawn --transpile-only src/index.ts",
@@ -31,12 +42,7 @@
     "lint": "eslint . --ext .ts",
     "format": "prettier --write \"src/**/*.ts\" \"tests/**/*.ts\"",
     "prepare": "husky install",
-    "commit": "cz",
-    "release": "standard-version",
-    "release:minor": "standard-version --release-as minor",
-    "release:patch": "standard-version --release-as patch",
-    "release:major": "standard-version --release-as major",
-    "release:dryrun": "standard-version --dry-run"
+    "commit": "cz"
   },
   "keywords": [
     "azure-devops",
@@ -69,7 +75,6 @@
     "husky": "^8.0.3",
     "jest": "^29.0.0",
     "prettier": "^3.0.0",
-    "standard-version": "^9.5.0",
     "ts-jest": "^29.0.0",
     "ts-node-dev": "^2.0.0",
     "typescript": "^5.8.2"

package.json

@@ -1,5 +1,25 @@
 ## Completed Tasks
 
+- [x] **Task**: Migrate release automation to use Release Please for version management (GitHub Issue #113)
+  - **Role**: DevOps Engineer
+  - **Phase**: Completed
+  - **Notes**:
+    - Implemented a new Release Please GitHub Action workflow
+    - Created Release Please configuration and manifest files
+    - Updated package.json to remove standard-version scripts and add Release Please config
+    - Deprecated the existing manual release workflow
+    - Added comprehensive documentation for the migration
+    - Updated CONTRIBUTING.md to reflect the new release process
+  - **Sub-tasks**:
+    - [x] Created .github/workflows/release-please.yml
+    - [x] Created .github/release-please-config.json
+    - [x] Created .github/release-please-manifest.json
+    - [x] Updated package.json to remove standard-version
+    - [x] Marked existing release.yml as deprecated
+    - [x] Updated CONTRIBUTING.md with new process
+    - [x] Created migration guide in docs/release-please-migration.md
+  - **Completed**: April 2, 2025
+
 - [x] **Task**: Implement get_project_details core functionality (GitHub Issue #101)
   - **Role**: Full-Stack Developer
   - **Phase**: Completed