-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Conversation
**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
This reverts commit d60f23e.
There was a problem hiding this 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) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
**What this PR does / why we need it**: Fixes a typo in #11789
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 branchWhich issue(s) this PR fixes:
Re #11332