Skip to content

fix(ado-pipelines): correct counter() to compile-time $(...) syntax #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ldastey-dev merged 1 commit into from
Jul 3, 2026
Merged

fix(ado-pipelines): correct counter() to compile-time $(...) syntax #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion standards/ado-pipelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -310,7 +310,7 @@ The pipeline `name:` and the resulting `Build.BuildNumber` are a **separate mech
| New feature or stage added | Add new deploy stage | `1.2.4 → 1.3.0` |
| Incompatible breaking change | Remove existing endpoint | `1.3.0 → 2.0.0` |

**Automated versioning.** Separate the two mechanisms. For the run identifier, prefer an automated source — `$[counter(...)]` for a monotonic build counter, or GitVersion where richer version derivation is needed — so `Build.BuildNumber` needs no manual maintenance. Reserve manual SemVer maintenance for the declared release/version variable (§13.1), where the MAJOR/MINOR/PATCH decision reflects a deliberate human judgement about the nature of the change that no counter can infer.
**Automated versioning.** Separate the two mechanisms. For the run identifier, prefer an automated source — `$(counter(...))` for a monotonic build counter, or GitVersion where richer version derivation is needed — so `Build.BuildNumber` needs no manual maintenance. Reserve manual SemVer maintenance for the declared release/version variable (§13.1), where the MAJOR/MINOR/PATCH decision reflects a deliberate human judgement about the nature of the change that no counter can infer.

### 13.3 · Version Bump Commits

Expand Down