From e377fc68a14d7129cb52b3ca5762d203485ba464 Mon Sep 17 00:00:00 2001 From: Pavlos Rontidis Date: Tue, 14 Jan 2025 14:10:40 -0500 Subject: [PATCH] chore(releasing): tweak release templates --- .github/ISSUE_TEMPLATE/minor-release.md | 1 + .github/ISSUE_TEMPLATE/patch-release.md | 1 + 2 files changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/minor-release.md b/.github/ISSUE_TEMPLATE/minor-release.md index a53f778b303c3..dcc1adfca7e48 100644 --- a/.github/ISSUE_TEMPLATE/minor-release.md +++ b/.github/ISSUE_TEMPLATE/minor-release.md @@ -54,6 +54,7 @@ On the day of release: - The deployment is done by Amplify. You can see the [deployment logs here](https://dd-corpsite.datadoghq.com/logs?query=service%3Awebsites-vector%20branch%3Awebsite&agg_m=count&agg_m_source=base&agg_t=count&cols=host%2Cservice&fromUser=true&messageDisplay=inline&refresh_mode=sliding&storage=hot&stream_sort=time%2Casc&viz=stream). - [ ] Release Linux packages. See [`vector-release` usage](https://github.com/DataDog/vector-release#usage). + - Note: the pipeline inputs are the version number `v0.` and a personal GitHub token. - [ ] Manually trigger the `trigger-package-release-pipeline-prod-stable` job. - [ ] Release updated Helm chart. See [releasing Helm chart](https://github.com/vectordotdev/helm-charts#releasing). - [ ] Once Helm chart is released, updated Vector manifests diff --git a/.github/ISSUE_TEMPLATE/patch-release.md b/.github/ISSUE_TEMPLATE/patch-release.md index 044c5013d5c68..197b787f5186e 100644 --- a/.github/ISSUE_TEMPLATE/patch-release.md +++ b/.github/ISSUE_TEMPLATE/patch-release.md @@ -39,6 +39,7 @@ On the day of release: - [ ] Wait for release workflow to complete - Discoverable via [https://github.com/timberio/vector/actions/workflows/release.yml](https://github.com/timberio/vector/actions/workflows/release.yml) - [ ] Release Linux packages. See [`vector-release` usage](https://github.com/DataDog/vector-release#usage). + - Note: the pipeline inputs are the version number `v0.` and a personal GitHub token. - [ ] Manually trigger the `trigger-package-release-pipeline-prod-stable` job. - [ ] Push the release branch to update the remote (This should close the preparation branch PR). - `git checkout v0. && git push`