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
{{ message }}
Repository navigation
Commit 20e33ec
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/minor-release.md
+13-35Lines changed: 13 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,44 +35,22 @@ closes the window automatically once both are done.
35
35
36
36
# Publish the release
37
37
38
-
-[ ] On release day, squash-merge the approved preparation PR directly into `master` using the
39
-
release-freeze bypass. Do not use the merge queue.
38
+
-[ ] On release day, squash-merge the approved preparation PR directly into `master` using admin
39
+
permissions (`Merge without waiting for requirements to be met (bypass rules)`). Do not use the merge queue.
40
40
41
-
The merge approves the release.[Tag approved release](https://github.com/vectordotdev/vector/actions/workflows/release_autotag.yml)
42
-
validates the squash-merge commit and creates the version tag and release branch at that exact commit.
41
+
The merge kicks off the[Tag approved release](https://github.com/vectordotdev/vector/actions/workflows/release_autotag.yml)
42
+
workflow, which creates the version tag and release branch at that exact commit.
43
43
The tag starts the release workflow; do not create the tag or release branch manually.
44
44
45
-
-[ ] Wait for release workflow to complete.
46
-
- Discoverable via [release.yml](https://github.com/vectordotdev/vector/actions/workflows/release.yml)
47
-
-[ ] Wait for the release workflow to reset the `website` branch to the release commit,
48
-
publishing the release notes to https://vector.dev
49
-
-[ ] Confirm that the release changelog was published to https://vector.dev/releases/
50
-
- Refer to the internal releasing doc to monitor the deployment.
45
+
-[ ] Wait for [release workflow](https://github.com/vectordotdev/vector/actions/workflows/release.yml) to complete.
46
+
- If it fails, use **Re-run failed jobs** to continue the release.
47
+
-[ ] Confirm that the release changelog was published to https://vector.dev/releases/
48
+
- Refer to the internal releasing doc to monitor the deployment.
49
+
-[ ] Confirm that [Homebrew](https://github.com/vectordotdev/homebrew-brew) was released ([workflow](https://github.com/vectordotdev/homebrew-brew/actions/workflows/release.yml))
51
50
-[ ] Release Linux packages. Refer to the internal releasing doc.
52
-
-[ ] Wait for the [Homebrew release](https://github.com/vectordotdev/homebrew-brew/actions/workflows/release.yml) to complete.
53
-
- The Vector release workflow starts it automatically after publishing a stable release.
54
-
It updates the ARM64 formula and commits directly to the tap's default branch, without a PR.
55
-
-[ ] Update the latest [release tag](https://github.com/vectordotdev/vector/releases) description with the release announcement.
56
51
57
-
# Post-release housekeeping
52
+
-[ ] Wait for the Helm chart [Post Release](https://github.com/vectordotdev/helm-charts/actions/workflows/release-post.yml) to complete.
53
+
- See [releasing Helm chart](https://github.com/vectordotdev/helm-charts/blob/develop/RELEASING.md).
58
54
59
-
-[ ] Wait for the release workflow to push its post-release housekeeping directly to `master`.
60
-
It begins the next minor `-dev` version, restores VRL `main`, and refreshes licenses and documentation.
61
-
- If it fails, use **Re-run failed jobs**; this also starts the Helm release.
62
-
-[ ] Wait for the [Helm chart release](https://github.com/vectordotdev/helm-charts/actions/workflows/release-prepare.yml).
63
-
- It starts after housekeeping and pushes directly, without a PR.
64
-
See [releasing Helm chart](https://github.com/vectordotdev/helm-charts/blob/develop/RELEASING.md) if it fails.
65
-
-[ ] Wait for the Helm chart release to push the Kubernetes manifests directly to `master`.
66
-
- The chart release triggers [Refresh Kubernetes manifests](https://github.com/vectordotdev/vector/actions/workflows/release_manifests.yml),
67
-
which runs `cargo vdev build manifests` and, when the generated manifests differ,
68
-
commits and pushes them to `master` itself as the `vectordotdev-bot` — no PR, no review,
69
-
no merge queue. If the run reports no changes, the manifests already match the chart.
70
-
-[ ] Wait for the [Unfreeze master](https://github.com/vectordotdev/vector/actions/workflows/release_unfreeze.yml)
71
-
workflow to close the direct-push window after the manifests run succeeds.
72
-
- It removes the temporary `vectordotdev-bot`**Always** bypass from every ruleset in
73
-
`RELEASE_FREEZE_BOT_BYPASS`, then sets the `RELEASE_FREEZE_RULESET_ID` ruleset back to **Disabled**.
74
-
It waits for the "Release Suite" run and any pending release workflow first,
75
-
and gives up after ten minutes, leaving the freeze active.
76
-
- Run it manually with `workflow_dispatch` if the release never starts the manifests workflow, if that
77
-
run fails, or to retry a failed closeout.
78
-
A manual run makes the same checks unless you set `force`, which closes the window anyway.
55
+
-[ ] Wait for the Helm chart release to push the Kubernetes manifests directly to `master` ([workflow](https://github.com/vectordotdev/vector/actions/workflows/release_manifests.yml)).
56
+
-[ ] Wait for the [Unfreeze master](https://github.com/vectordotdev/vector/actions/workflows/release_unfreeze.yml) workflow to finalize the release.
0 commit comments