Skip to content

📖 [Docs]: Release bumps now have a configurable default - #196

Open
Marius Storhaug (MariusStorhaug) wants to merge 4 commits into
mainfrom
default-release-bump
Open

📖 [Docs]: Release bumps now have a configurable default#196
Marius Storhaug (MariusStorhaug) wants to merge 4 commits into
mainfrom
default-release-bump

Conversation

@MariusStorhaug

@MariusStorhaug Marius Storhaug (MariusStorhaug) commented Aug 29, 2026

Copy link
Copy Markdown
Member

Repositories can configure their normal semantic version bump through DefaultBump. Explicit owned bump labels override that policy, prereleases reuse the resolved bump, and release:skip remains the publication stop.

Changed: Release bumps have a safe repository default

DefaultBump accepts patch, minor, or major and resolves to patch when omitted. A pull request can override it with one owned bump label; conflicting owned labels fail, while bare and unrelated labels remain ignored.


Technical details
  • The Release Management specification and design define the configuration, resolution order, validation, and prerelease behavior.
  • Automation Labels, PR Format, Continuous Delivery and Release, Branching and Merging, Natural Language examples, and the VS Code Extension Framework use the same contract.
  • The optional workflow_dispatch path still requires an explicit bump and release-note context.
  • Empty pull requests and direct pushes remain excluded as ad hoc release interfaces.
  • Dependency-tool guidance, implementation repositories, and fleet labels are unchanged.
  • Issue convergence sweep: no open MSXOrg/docs issue matching DefaultBump, default bump, release label, or release management is fully satisfied by this diff.
Changed surface Standards checked Framework docs checked Result
src/docs/Capabilities/release-management/** Natural Language, Markdown Release Management Aligned
src/docs/Capabilities/vscode-extension-framework/** Natural Language, Markdown Release Management, VS Code Extension Framework Aligned
src/docs/Ways-of-Working/** Natural Language, Markdown Release Management Aligned
src/docs/Coding-Standards/Natural-Language.md Natural Language, Markdown Release Management Aligned
Relevant issues (or links)

Related work

@MariusStorhaug Marius Storhaug (MariusStorhaug) added the release:skip Validate the change without publishing a release. label Aug 29, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the MSX documentation set to introduce a configurable repository-wide default semantic version bump (DefaultBump) for release automation, while keeping owned release:* labels as explicit overrides and updating prerelease semantics to reuse the resolved bump.

Changes:

  • Define DefaultBump (defaulting to patch) and the override / conflict rules in Release Management spec + design.
  • Update Ways of Working guidance (PR format, CD/release, branching/promotion, automation labels) to reflect “policy-first” bump selection and prerelease behavior.
  • Align the VS Code Extension Framework spec/design with the Release Management contract.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
src/docs/Ways-of-Working/PR-Format.md Documents how release:pre-release interacts with DefaultBump and owned bump-label overrides.
src/docs/Ways-of-Working/Continuous-Delivery-And-Release.md Updates CD/release “decision at the gate” language to reference resolved release policy and DefaultBump.
src/docs/Ways-of-Working/Branching-and-Merging.md Updates promotion-model guidance to use the resolved policy / DefaultBump with explicit overrides.
src/docs/Ways-of-Working/Automation-Labels.md Reframes label meanings around DefaultBump + owned label overrides and conflict handling.
src/docs/Coding-Standards/Natural-Language.md Updates example language/error-message guidance to reflect conflicting owned bump labels and DefaultBump.
src/docs/Capabilities/vscode-extension-framework/spec.md Updates framework requirements/success criteria to match policy-driven bump selection.
src/docs/Capabilities/vscode-extension-framework/design.md Updates pipeline/design narrative to reference release policy and DefaultBump in version resolution.
src/docs/Capabilities/release-management/spec.md Defines the normative DefaultBump rules, override precedence, prerelease behavior, and label conflict handling.
src/docs/Capabilities/release-management/index.md Updates the section index descriptions to match the refreshed spec/design framing.
src/docs/Capabilities/release-management/design.md Documents configuration surface and pipeline behavior for resolving DefaultBump + owned label overrides.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread src/docs/Coding-Standards/Natural-Language.md Outdated
Comment thread src/docs/Ways-of-Working/Branching-and-Merging.md Outdated
Comment thread src/docs/Ways-of-Working/Automation-Labels.md Outdated
Comment thread src/docs/Capabilities/vscode-extension-framework/spec.md Outdated
Comment thread src/docs/Capabilities/vscode-extension-framework/design.md

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated no new comments.

@MariusStorhaug
Marius Storhaug (MariusStorhaug) marked this pull request as ready for review August 29, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:skip Validate the change without publishing a release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants