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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -555,9 +555,9 @@ This project follows the GitHub Community Guidelines. Please be respectful and i
555
555
556
556
Releases are defined in `.github/workflows/release.md` and triggered from the compiled GitHub Actions workflow.
557
557
558
-
The team follows semantic versioning on a best-effort basis.
558
+
The team follows a **weekly or bi-weekly minor release cadence**, similar to VS Code's release practices. Version numbers increment the minor component on each release cycle — not on the basis of change scope. Patch releases are reserved for urgent fixes between cycles; major releases are used for significant breaking changes only.
559
559
560
-
> **Note:** The release workflow publishes the new version as a **prerelease** on GitHub with `latest=false`. Prereleases are floated for a few days. On Monday, maintainers promote the last known good prerelease to stable so `latest` resolves to that release.
560
+
> **Note:** The release workflow publishes the new version as a **prerelease** on GitHub with `latest=false`. Prereleases are floated for a few days. On Monday, maintainers promote the last known good prerelease to stable so `latest` resolves to that release. Immediately after promotion, a new minor pre-release is kicked off to start the next cycle.
561
561
562
562
### Steps
563
563
@@ -589,10 +589,17 @@ The team follows semantic versioning on a best-effort basis.
589
589
590
590
Users who install with `version: latest` (the default) will now receive the new release.
591
591
592
+
5.**Start the next release cycle**_(immediately after promotion)_
593
+
594
+
Following the weekly/bi-weekly cadence, kick off a new `minor` release right after promoting the previous one to stable. Repeat steps 1–3 to publish it as a prerelease. This prerelease then floats until the next Monday, when it becomes the new stable release.
595
+
596
+
> [!TIP]
597
+
> Always select `minor` when starting a new cycle. Use `patch` only for urgent fixes within a cycle, and `major` only for significant breaking changes.
598
+
592
599
### Summary
593
600
594
601
```
595
-
Launch release action
602
+
Launch release action (minor)
596
603
│
597
604
▼
598
605
Workflow pushes tag & pauses
@@ -609,11 +616,14 @@ Approve the gh-aw-actions-release environment gate
609
616
▼
610
617
Release published as prerelease 🎉
611
618
│
612
-
▼ (manual)
619
+
▼ (Monday — manual)
613
620
Promote prerelease → full release on GitHub Releases page
614
621
│
615
622
▼
616
623
'latest' now resolves to the new version ✅
624
+
│
625
+
▼ (same day — start next cycle)
626
+
Launch next minor release action → new prerelease published
0 commit comments