Skip to content

Commit 9b5889d

Browse files
jvoravongcrobert-1
andauthored
[chore] Improve RELEASE.md (#1745)
* Update RELEASE.md * Update RELEASE.md Co-authored-by: Curtis Robert <[email protected]> --------- Co-authored-by: Curtis Robert <[email protected]>
1 parent 8437486 commit 9b5889d

File tree

1 file changed

+14
-7
lines changed

1 file changed

+14
-7
lines changed

RELEASE.md

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,20 @@ of `version` field.
1515

1616
#### Using GitHub Workflows
1717

18-
- **Manual Dispatch Github Worfklow:**
19-
- Navigate to the **[Release Drafter](https://github.com/signalfx/splunk-otel-collector-chart/actions/workflows/release_drafter.yaml** workflow under GitHub Actions.
20-
- Manually trigger the workflow. It automatically drafts a PR for the release.
21-
- Review code changes, validate chart functionality, approve the PR, and merge the PR.
22-
- **Automatic Schedule Github Worfklow:**
23-
- Automatically generated PRs are scheduled to follow collector releases.
24-
- Review code changes, validate chart functionality, approve the PR, and merge the PR.
18+
1. When a new upstream collector release is available, the [Release Drafter workflow](https://github.com/signalfx/splunk-otel-collector-chart/actions/workflows/release_drafter.yaml) automatically creates a release PR every 12 hours at **00:55 UTC and 12:55 UTC**.
19+
- This schedule corresponds to:
20+
- **5:55 AM / 5:55 PM** during Daylight Saving Time (PDT / UTC−7)
21+
- **4:55 AM / 4:55 PM** during Standard Time (PST / UTC−8)
22+
- To trigger the workflow outside the scheduled times, use the ["Run workflow" button](https://github.com/signalfx/splunk-otel-collector-chart/actions/workflows/release_drafter.yaml) with default input parameters.
23+
1. After the [release PR](https://github.com/signalfx/splunk-otel-collector-chart/pulls?q=is%3Apr+is%3Aopen+%22Prepare+Release%22) is created:
24+
- Review the code changes
25+
- Ensure all checks have passed to validate chart functionality
26+
- Note: Due to a GitHub limitation, PRs created by workflows may not trigger downstream checks automatically. A repository approver may need
27+
to close and reopen the PR to kick off the required checks. This is a known issue we’re working to improve.
28+
- Approve and merge the PR
29+
1. The [Release Charts workflow](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/.github/workflows/release.yaml) will publish the release shortly after.
30+
- That’s it — you’re done!
31+
- _Automation prevents duplicate or invalid releases. If a release isn’t created, you can check for failed workflow run info [here](https://github.com/signalfx/splunk-otel-collector-chart/actions/workflows/release.yaml)._
2532

2633
#### Manually Making a Release
2734

0 commit comments

Comments
 (0)