Skip to content
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

feat: add release please config (#11333) #11789

Merged
merged 4 commits into from
Jan 26, 2024

Conversation

trevorwhitney
Copy link
Collaborator

What this PR does / why we need it:

The new release process is being developed in another repo for now as it enables much faster feedback loops. We are at the stage where we are pulling the Loki repo and building images, so it's time to move the release-please config into Loki, and configure it for the various packages we will be releasing.

This PR adds the two basic configs that release-please requires. This PR does not change anything about the release process, it just enables us to keep iterating out of band until we're ready to move over.

This was already added to main, but adding here so I can test it on the release branch

Which issue(s) this PR fixes:
Re #11332

**What this PR does / why we need it**:

The new release process is being developed in another repo for now as it
enables much faster feedback loops. We are at the stage where we are
pulling the Loki repo and building images, so it's time to move the
`release-please` config into Loki, and configure it for the various
packages we will be releasing.

This PR adds the two basic configs that `release-please` requires. This
PR does not change anything about the release process, it just enables
us to keep iterating out of band until we're ready to move over.

**Which issue(s) this PR fixes**:
Re #11332
@trevorwhitney trevorwhitney requested a review from a team as a code owner January 25, 2024 20:14
@pull-request-size pull-request-size bot added size/L and removed size/M labels Jan 25, 2024
Copy link
Contributor

@MichelHollands MichelHollands left a comment

Choose a reason for hiding this comment

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

One nit about a variable name

dist: clean
ifeq ($(SKIP_ARM),true)
Copy link
Contributor

Choose a reason for hiding this comment

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

(nit) The name SKIP_ARM is a bit misleading. You're swapping arm for Intel here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

intel is being built in either case, so the guard is to whether only to build intel, or whether to build intel and arm, unless I'm missing something? problem is GitHub actions don't support arm yet, so we need a way to disable those archs specifically

@trevorwhitney trevorwhitney merged commit e628f5d into release-2.9.x Jan 26, 2024
4 checks passed
@trevorwhitney trevorwhitney deleted the add-release-jobs-to-2.9.x branch January 26, 2024 21:59
trevorwhitney added a commit that referenced this pull request Jan 26, 2024
**What this PR does / why we need it**:

Fixes a typo in #11789
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants