Skip to content
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.

Use goreleaser to build weekly releases #576

Merged

Conversation

simonswine
Copy link
Collaborator

Those releases power the Grafana Labs internal roll-outs, that occur
weekly into our production systems.

Goreleaser is used to build those releases with the same config that is
used for the project releases.

To get around some limitations around semver in goreleaser we have to
imitate a version with local git tags.

Those releases power the Grafana Labs internal roll-outs, that occur
weekly into our production systems.

Goreleaser is used to build those releases with the same config that is
used for the project releases.

To get around some limitations around semver in goreleaser we have to
imitate a version with local git tags.
@simonswine simonswine marked this pull request as ready for review March 10, 2023 10:53
@simonswine simonswine enabled auto-merge (squash) March 10, 2023 11:23
Copy link
Collaborator

@cyriltovena cyriltovena left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@simonswine simonswine merged commit af8b921 into grafana:main Mar 10, 2023
simonswine added a commit to simonswine/pyroscope that referenced this pull request Jun 30, 2023
Those releases power the Grafana Labs internal roll-outs, that occur
weekly into our production systems.

Goreleaser is used to build those releases with the same config that is
used for the project releases.

To get around some limitations around semver in goreleaser we have to
imitate a version with local git tags.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants