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

Release tooling: Fix new patch labels #23409

Merged
merged 4 commits into from
Jul 12, 2023
Merged

Conversation

JReinhold
Copy link
Contributor

This cherry-picks the fix that pointed at main. It worked.

(cherry picked from commit 1396344)

What I did

How to test

Checklist

  • Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
  • Make sure to add/update documentation regarding your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Maintainers

  • If this PR should be tested against many or all sandboxes,
    make sure to add the ci:merged or ci:daily GH label to it.
  • Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

Release tooling: Fix new patch labels

(cherry picked from commit 1396344)
@JReinhold JReinhold self-assigned this Jul 11, 2023
@JReinhold JReinhold added build Internal-facing build tooling & test updates patch:no labels Jul 11, 2023
@JReinhold
Copy link
Contributor Author

For some reason the snapshot changes weren't cherry picked, even though they were part of the same commit. super confused, but I just updated them manually.

@JReinhold JReinhold merged commit 204eb01 into next Jul 12, 2023
@JReinhold JReinhold deleted the cherry-pick-patch-label-fix branch July 12, 2023 08:52
@github-actions github-actions bot mentioned this pull request Jul 12, 2023
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Internal-facing build tooling & test updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants