Skip to content

Commit e3553fa

Browse files
authored
[chore] update release.md (#12942)
#### Description Update release schedule & mention missing images in Dockerhub
1 parent 8c5e7ff commit e3553fa

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/release.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -114,13 +114,13 @@ The last step of the release process creates artifacts for the new version of th
114114

115115
5. Ensure the "Release Core", "Release Contrib", "Release k8s", and "Builder - Release" actions pass, this will
116116

117-
1. push new container images to `https://hub.docker.com/repository/docker/otel/opentelemetry-collector`, `https://hub.docker.com/repository/docker/otel/opentelemetry-collector-contrib` and `https://hub.docker.com/repository/docker/otel/opentelemetry-collector-k8s`
117+
1. ~~push new container images to `https://hub.docker.com/repository/docker/otel/opentelemetry-collector`, `https://hub.docker.com/repository/docker/otel/opentelemetry-collector-contrib` and `https://hub.docker.com/repository/docker/otel/opentelemetry-collector-k8s`~~ Currently we cannot publish images to Dockerhub due to rate limiting http://github.com/open-telemetry/community/issues/2641.
118118

119119
2. create a Github release for the tag and push all the build artifacts to the Github release. See [example](https://github.com/open-telemetry/opentelemetry-collector-releases/actions/workflows/release-core.yaml).
120120

121121
3. build and release ocb binaries under a separate tagged Github release, e.g. `cmd/builder/v0.85.0`
122122

123-
4. build and push ocb Docker images to `https://hub.docker.com/r/otel/opentelemetry-collector-builder` and the GitHub Container Registry within the releases repository
123+
4. ~~build and push ocb Docker images to `https://hub.docker.com/r/otel/opentelemetry-collector-builder` and the GitHub Container Registry within the releases repository~~
124124

125125
6. Update the release notes with the CHANGELOG.md updates.
126126

@@ -217,7 +217,6 @@ Once a module is ready to be released under the `1.x` version scheme, file a PR
217217

218218
| Date | Version | Release manager |
219219
|------------|----------|------------------------------------------------------|
220-
| 2025-04-28 | v0.125.0 | [@songy23](https://github.com/songy23) |
221220
| 2025-05-12 | v0.126.0 | [@dmitryax](https://github.com/dmitryax) |
222221
| 2025-05-26 | v0.127.0 | [@codeboten](https://github.com/codeboten) |
223222
| 2025-06-09 | v0.128.0 | [@bogdandrutu](https://github.com/bogdandrutu) |
@@ -227,3 +226,4 @@ Once a module is ready to be released under the `1.x` version scheme, file a PR
227226
| 2025-08-11 | v0.132.0 | [@evan-bradley](https://github.com/evan-bradley) |
228227
| 2025-08-25 | v0.133.0 | [@TylerHelmuth](https://github.com/TylerHelmuth) |
229228
| 2025-09-08 | v0.134.0 | [@atoulme](https://github.com/atoulme) |
229+
| 2025-09-22 | v0.135.0 | [@songy23](https://github.com/songy23) |

0 commit comments

Comments
 (0)