多分支多开发者环境下自动版本编号方案咨询

Hey Richard, great question—automating version numbering for your team’s workflow is a smart move to cut down on manual errors and keep everyone aligned across your dev/staging/live branches. Let’s walk through a practical setup tailored to your stack (BitBucket, VS Code, OSX, multi-developer environment):

First, get your team on the same page with Semantic Versioning (SemVer) — it’s industry-standard and works perfectly for parallel development. The format is MAJOR.MINOR.PATCH:

• MAJOR: Breaking, backward-incompatible changes (e.g., v2.0.0 when you rewrite an API)
• MINOR: New features that don’t break existing functionality (e.g., v1.1.0 when you add a user profile page)
• PATCH: Bug fixes or small tweaks (e.g., v1.0.1 when you fix a login form error)
  For pre-release branches (dev/staging), add suffixes like -dev.1 or -rc.1 to make environments clear.

BitBucket’s built-in CI/CD pipelines are perfect for triggering automatic version updates when code merges to your branches. Here’s a step-by-step setup:

Use a Versioning Tool #

We’ll use standard-version (a Node.js tool, easy to install on OSX) — it reads your commit messages to automatically bump the right version number. For Python projects, bumpversion works just as well (install via Homebrew with brew install bumpversion).

Example BitBucket Pipeline Config #

Create a bitbucket-pipelines.yml file in your project root to define branch-specific versioning rules:

image: node:18 # Use a Python image if using bumpversion

pipelines:
  branches:
    dev:
      - step:
          name: Bump Dev Pre-Release Version
          script:
            - npm install -g standard-version
            # Bump to a dev pre-release (e.g., 1.0.0-dev.1 → 1.0.0-dev.2)
            - standard-version --prerelease dev
            - git push origin dev --tags # Push the new version and tag to BitBucket
    staging:
      - step:
          name: Bump Release Candidate Version
          script:
            - npm install -g standard-version
            # Bump to a release candidate (e.g., 1.0.0-rc.1)
            - standard-version --prerelease rc --release-as minor # Adjust to major/patch as needed
            - git push origin staging --tags
    live:
      - step:
          name: Bump Production Version
          script:
            - npm install -g standard-version
            # Bump to a full production release (e.g., 1.0.0 → 1.1.0)
            - standard-version
            - git push origin live --tags

To make this work smoothly for parallel development, set up your team’s local environments:

• Install the tool locally: Every dev runs npm install -g standard-version (or brew install bumpversion) on their OSX machine.
• Use Conventional Commits: Train your team to write commit messages that follow the Conventional Commits format (e.g., feat: add password reset or fix: resolve checkout crash). This is how standard-version knows whether to bump a major/minor/patch version.
  • VS Code shortcut: Install the Conventional Commits plugin to auto-generate compliant commit messages.
• Branch hygiene: Each dev works on feature branches pulled from dev, opens a PR to dev when done. Merging the PR triggers the dev pipeline to bump the version automatically.

With multiple devs merging code, here’s how to prevent version number conflicts:

• Enable Pipeline locking in BitBucket so only one version bump runs at a time for a branch.
• Ask devs to pull the latest dev branch before opening a PR — this ensures their local version file is up-to-date.
• If a conflict does happen, the pipeline will fail; just have a dev resolve the version file conflict locally and push a fix.

• Version Lens: Shows you the current version number directly in your package.json (or setup.py) and highlights if it’s out of sync with the repo.
• GitLens: Helps track who last modified the version file, making it easier to debug conflicts.

This setup takes the guesswork out of versioning, keeps your branch versions consistent, and eliminates manual version edits entirely.

内容的提问来源于stack exchange，提问作者Richard