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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: release release-2.8.x #12043

Merged
merged 1 commit into from
Feb 23, 2024
Merged

chore: release release-2.8.x #12043

merged 1 commit into from
Feb 23, 2024

Conversation

grafanabot
Copy link
Collaborator

馃 I have created a release beep boop

2.8.9

2.8.9 (2024-02-22)

Bug Fixes

Merging this PR will release the artifacts of 9db9a3e

@grafanabot grafanabot force-pushed the release-please--branches--release-2.8.x branch from 46a16e3 to df75cc5 Compare February 22, 2024 23:14
@grafanabot grafanabot requested a review from a team as a code owner February 22, 2024 23:14
@grafanabot grafanabot added autorelease: pending backport main Tag a PR with this label to create a PR which cherry pics it into the main branch type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories labels Feb 22, 2024
@github-actions github-actions bot removed the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Feb 22, 2024
@grafanabot
Copy link
Collaborator Author

This PR must be merged before a backport PR will be created.

1 similar comment
@grafanabot
Copy link
Collaborator Author

This PR must be merged before a backport PR will be created.

@grafanabot grafanabot added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Feb 23, 2024
@grafanabot grafanabot force-pushed the release-please--branches--release-2.8.x branch from df75cc5 to c95da4e Compare February 23, 2024 17:27
@github-actions github-actions bot removed the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Feb 23, 2024
@grafanabot
Copy link
Collaborator Author

This PR must be merged before a backport PR will be created.

trevorwhitney
trevorwhitney approved these changes Feb 23, 2024
View reviewed changes
Copy link
Collaborator

@trevorwhitney trevorwhitney left a comment

Choose a reason for hiding this comment

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

:shipit:

@trevorwhitney trevorwhitney merged commit 78f7684 into release-2.8.x Feb 23, 2024
7 checks passed
@trevorwhitney trevorwhitney deleted the release-please--branches--release-2.8.x branch February 23, 2024 17:35
@grafanabot
Copy link
Collaborator Author

Hello @trevorwhitney!
Backport pull requests need to be either:

  • Pull requests which address bugs,
  • Urgent fixes which need product approval, in order to get merged,
  • Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

@grafanabot
Copy link
Collaborator Author

馃 Release is at https://github.com/grafana/loki/releases/tag/untagged-e5a4801e532d6818a066 馃尰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@trevorwhitney trevorwhitney trevorwhitney approved these changes

Assignees
No one assigned
Labels
autorelease: tagged backport main Tag a PR with this label to create a PR which cherry pics it into the main branch missing-labels size/XS
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@grafanabot @trevorwhitney