Skip to content

Improve description of the release process #1380

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 12, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,11 @@ The release process is almost entirely managed by [GitHub actions](https://githu

1. Create a new tag for the layer to publish. For example, to create a new collector layer, the following command is used:
`git tag layer-collector/0.0.8`
2. Push the tag to [opentelemetry-lambda](https://github.com/open-telemetry/opentelemetry-lambda) repository to trigger the publish action.
2. Push the tag to [opentelemetry-lambda](https://github.com/open-telemetry/opentelemetry-lambda) repository to trigger the publish action:
`git push origin tag layer-collector/0.0.8`
3. Wait for the [release workflow](https://github.com/open-telemetry/opentelemetry-lambda/actions/workflows/release-layer-collector.yml) to finish.
4. Create a release in https://github.com/open-telemetry/opentelemetry-lambda/releases/new
* Select a the newly pushed tag
* Select the corresponding previous release
* Click "Generate Release Notes"
* Adjust the release notes. Include the ARN, list of changes and diff with previous label.
Loading