fix: allow feat commits to bump minor version in pre-1.0.0 releases

Remove bump-patch-for-minor-pre-major setting to restore standard
semantic versioning behavior for pre-1.0.0 versions.

With this change:
- feat: commits bump minor version (0.1.1 → 0.2.0)
- BREAKING CHANGE: commits bump minor version (0.1.1 → 0.2.0)
- fix: commits bump patch version (0.1.1 → 0.1.2)

Previously, bump-patch-for-minor-pre-major caused feat: commits
to only bump patch versions, which prevented proper version
signaling for new features in pre-1.0.0 releases.

Author: jcouball

.release-please-config.json

@@ -4,7 +4,6 @@
     ".": {
       "release-type": "node",
       "bump-minor-pre-major": true,
-      "bump-patch-for-minor-pre-major": true,
       "changelog-path": "CHANGELOG.md",
       "include-component-in-tag": false,
       "pull-request-title-pattern": "chore: release v${version}",

REQUIREMENTS.md

@@ -2342,165 +2342,9 @@ Runs on schedule (weekly) and on pull requests.
 - Weekly scheduled run (every Monday)
 - On pull requests that modify `package.json` or `package-lock.json`
 
-### 9.2 Release Management with release-please
+### 9.2 Marketplace Publishing Requirements
 
-**Tool:** [release-please](https://github.com/googleapis/release-please) by Google
-
-**Strategy:** Conventional Commits + Automated Changelog
-
-#### 9.2.1 Release Please Configuration
-
-**Commit Convention:** [Conventional Commits](https://www.conventionalcommits.org/)
-
-**Required Commit Types:**
-
-- `feat:` - New feature (triggers MINOR version bump)
-- `fix:` - Bug fix (triggers PATCH version bump)
-- `docs:` - Documentation changes (no version bump)
-- `chore:` - Maintenance tasks (no version bump)
-- `test:` - Test changes (no version bump)
-- `refactor:` - Code refactoring (no version bump)
-- `BREAKING CHANGE:` - Breaking change (triggers MAJOR version bump)
-  - Include in commit footer or use `!` suffix: `feat!:`
-
-**Example Commits:**
-
-```text
-feat: add support for named section snippets
-
-fix: resolve path traversal vulnerability in symlink handling
-
-docs: update README with new toggle commands
-
-feat!: change default preview state to 'off'
-BREAKING CHANGE: Users who relied on previews being on by default will need to update settings
-```
-
-**Configuration File:** `.release-please-manifest.json`
-
-```json
-{
-  ".": "0.0.1"
-}
-```
-
-**Config File:** `release-please-config.json`
-
-```json
-{
-  "packages": {
-    ".": {
-      "release-type": "node",
-      "package-name": "mkdocs-snippet-lens",
-      "changelog-path": "CHANGELOG.md",
-      "bump-minor-pre-major": true,
-      "bump-patch-for-minor-pre-major": true,
-      "extra-files": [
-        "package.json"
-      ]
-    }
-  }
-}
-```
-
-#### 9.2.2 Release Workflow (`release.yml`)
-
-**Trigger:** On push to `main` branch
-
-**Jobs:**
-
-1. **Create or Update Release PR**
-   - Use `google-github-actions/release-please-action`
-   - Analyzes commits since last release
-   - Creates/updates a release PR with:
-     - Updated version in `package.json`
-     - Updated `CHANGELOG.md` with all changes
-     - Git tag for the new version
-   - Groups related changes by type (Features, Bug Fixes, etc.)
-
-2. **Build and Publish** (runs only when release PR is merged)
-   - Triggered by release-please creating a GitHub Release
-   - Runs on `ubuntu-latest` only (publishing needs single run)
-   - Steps:
-     1. Checkout code at release tag
-     2. Install dependencies (`npm ci`)
-     3. Run tests (`npm test`)
-     4. Build production package (`npm run package`)
-     5. Publish to VS Code Marketplace using `@vscode/vsce`
-     6. Upload .vsix to GitHub Release as asset
-
-**Required Secrets:**
-
-- `VSCE_PAT` - Personal Access Token for VS Code Marketplace publishing
-  - Obtained from Azure DevOps for VS Code Marketplace
-  - Stored in GitHub repository secrets
-  - Scoped to marketplace publishing only
-
-**Example Workflow Structure:**
-
-```yaml
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  release-please:
-    runs-on: ubuntu-latest
-    outputs:
-      release_created: ${{ steps.release.outputs.release_created }}
-      tag_name: ${{ steps.release.outputs.tag_name }}
-    steps:
-      - uses: google-github-actions/release-please-action@v4
-        id: release
-        with:
-          release-type: node
-          package-name: mkdocs-snippet-lens
-
-  publish:
-    needs: release-please
-    if: ${{ needs.release-please.outputs.release_created }}
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-      - run: npm ci
-      - run: npm test
-      - run: npm run package
-      - run: npx @vscode/vsce publish -p ${{ secrets.VSCE_PAT }}
-      - uses: actions/upload-release-asset@v1
-        # Upload .vsix to GitHub Release
-```
-
-#### 9.2.3 Version Management
-
-**Versioning Scheme:** Semantic Versioning (SemVer)
-
-- **Format:** MAJOR.MINOR.PATCH (e.g., 1.2.3)
-- **Initial Version:** 0.1.0 (pre-1.0 for initial development)
-- **Pre-1.0 Behavior:**
-  - Minor bumps for new features
-  - Patch bumps for bug fixes
-  - Breaking changes allowed without major bump (0.x.y is unstable)
-- **Post-1.0 Behavior:**
-  - Strict SemVer compliance
-  - MAJOR for breaking changes
-  - MINOR for new features
-  - PATCH for bug fixes
-
-**Version Sources:**
-
-- Single source of truth: `package.json` `version` field
-- Automatically updated by release-please
-- Git tags created automatically (e.g., `v1.2.3`)
-
-### 9.3 Marketplace Publishing Requirements
-
-#### 9.3.1 Pre-Publish Checklist
+#### 9.2.1 Pre-Publish Checklist
 
 Before first marketplace publication, ensure:
 
@@ -2520,7 +2364,7 @@ Before first marketplace publication, ensure:
   - `bugs`
   - `license`
 
-#### 9.3.2 Publishing Process
+#### 9.2.2 Publishing Process
 
 **Manual First Release:**