mirror of https://github.com/grafana/loki
Publish tagged images of loki-canary-boringcrypto (#10386)
**What this PR does / why we need it**:
Examining the images contained in the loki-canary repo (
https://hub.docker.com/repository/docker/grafana/loki-canary/tags?page=1&ordering=last_updated
) compared to the loki-canary-boringcrypto repo (
https://hub.docker.com/repository/docker/grafana/loki-canary-boringcrypto/tags?page=1&ordering=last_updated
), it appears that the explicitly tagged images (such as 'main') are not
being sent to the boringcrypto repo.
This PR is to adjust that behavior so that both repos receive the same
number of builds (one will be boringcrypto enabled, the other will not
be)
**Which issue(s) this PR fixes**:
Fixes #<issue number>
**Special notes for your reviewer**:
**Checklist**
- [ ] Reviewed the
[`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md)
guide (**required**)
- [ ] Documentation added
- [ ] Tests updated
- [ ] `CHANGELOG.md` updated
- [ ] If the change is worth mentioning in the release notes, add
`add-to-release-notes` label
- [ ] Changes that require user attention or interaction to upgrade are
documented in `docs/sources/setup/upgrade/_index.md`
- [ ] For Helm chart changes bump the Helm chart version in
`production/helm/loki/Chart.yaml` and update
`production/helm/loki/CHANGELOG.md` and
`production/helm/loki/README.md`. [Example
PR](d10549e3ec
)
pull/8962/head^2
parent
94a5f94cf4
commit
11f4906223
Loading…
Reference in new issue