You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat(release): channel-aware workflows + RELEASING runbook
Phase 1 of the release-strategy work.
- Add scripts/extract-release-notes.ps1: shared CHANGELOG section
extractor consumed by all three release workflows.
- release-psdocs.yml / release-psdocs-azure.yml:
- Parse tag into base version + optional preview suffix.
- Validate base version against PSDocs.psd1 / PSDocs.Azure.psd1
ModuleVersion (fail fast on mismatch).
- Extract per-version notes from CHANGELOG.md and pass via
--notes-file to gh release create.
- Mark GitHub Release as --prerelease when tag carries a SemVer
prerelease suffix.
- release-vscode.yml:
- Two-tag-prefix design (vscode-v* stable + vscode-preview-v*
preview) because VS Marketplace does not accept SemVer
prerelease suffixes in package.json version.
- Validate version against package.json.
- Route channel through the build's existing -Channel param so
preview publishes as vicperdana.psdocs-vscode-preview.
- Add RELEASING.md: end-to-end runbook covering one-time secret +
environment setup (PSGALLERY_API_KEY, VSCE_PAT, release env with
required reviewers), per-package release steps, pre-release flow,
troubleshooting, and rollback.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs: link RELEASING runbook + clean up legacy ADO release doc
Phase 1 finish + Phase 2 of the release-strategy work.
- README.md: add 'see RELEASING.md' line under 'Changes and versioning'.
- CONTRIBUTING.md: replace stale 'docs/release.md' link with link to
RELEASING.md.
- docs/release.md: replace ADO-flavored release doc (referenced obsolete
Azure DevOps build numbers like 0.2.0-B2103003) with a stub pointing
to RELEASING.md.
- docs/publish/devops-wiki.md: page was a 'Coming soon' stub; expand it
with both Azure Pipelines and GitHub Actions tabs covering the same
scenario, matching the convention used elsewhere in the docs.
- MONOREPO_MIGRATION.md: under 'Future Subtree Updates', add a callout
reminding maintainers to delete upstream .azure-pipelines/ and nested
.github/ directories after each subtree pull (the monorepo uses GH
Actions only at the repo root).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat(release): dry-run trigger + PSDocs manifest URIs to monorepo
Phase 3 code-side work for the release-strategy.
- Add workflow_dispatch trigger to all three release-*.yml workflows
with two inputs: 'tag' (string, required) and 'dry_run' (boolean,
default true). When dry_run=true the workflows still parse the tag,
validate the manifest, extract CHANGELOG notes, and build the
package, but skip Publish-Module / vsce publish / gh release create
and instead print a summary step. Lets maintainers sanity-check a
release end-to-end without producing any artifacts on PSGallery,
the VS Marketplace, or GitHub Releases.
- Replace 'github.ref_name' with 'inputs.tag || github.ref_name' so
push and dispatch paths share one code path.
- packages/psdocs/src/PSDocs/PSDocs.psd1: redirect ProjectUri,
LicenseUri, and ReleaseNotes from microsoft/PSDocs to the new
monorepo (Azure/PSDocs.Azure/tree/main/packages/psdocs and the
package's CHANGELOG). PSDocs.Azure.psd1 was already correct.
- RELEASING.md: add a 'Pre-flight: dry-run' section that explains
when and how to use the new dispatch trigger.
Write-Error "package.json version '$($pkg.version)' does not match tag version '$expected'. Update packages/vscode-extension/package.json before tagging."
88
+
exit 1
89
+
}
90
+
Write-Host "package.json version '$($pkg.version)' matches tag '$expected'."
0 commit comments