chore(publish): [v8] Use craft config from merge target branch for release preparation #10764
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lms24
changed the title
mydea
approved these changes
Feb 21, 2024
|
This depends on getsentry/publish#3469. Converting to draft for the moment to avoid accidental merges |
|
Merging now as getsentry/publish#3469 was merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Same principle as in #10763 but with config from v8 and releasing from
master.This isn't strictly necessary but I'd say, we also change this to take the config from
masterbecause technically, our default branch isdevelopand the config could diverge. Unlikely but still something I'd say we should do now that we can.ref getsentry/publish#3441