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

docs: Loki 3.0 Release Notes #12508

Merged
merged 3 commits into from
Apr 8, 2024
Merged

docs: Loki 3.0 Release Notes #12508

merged 3 commits into from
Apr 8, 2024

Conversation

JStickler
Copy link
Contributor

What this PR does / why we need it:

Collects content from "next.md", RADS, and CHANGELOG into a draft for the next Release Notes.

@JStickler JStickler added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Apr 8, 2024
@JStickler JStickler requested a review from a team as a code owner April 8, 2024 15:53
@grafanabot
Copy link
Collaborator

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

@trevorwhitney
Copy link
Collaborator

FYI: 3.0 is released with partial release notes, we'll need to copy these over to the GH release when ready to go


- [Deprecated storage options](https://grafana.com/docs/loki/latest/storage/) including the deprecation of the BoltDB store.

- [Deprecated configuration options](https://grafana.com/docs/loki/next/configure/).
Copy link
Collaborator

Choose a reason for hiding this comment

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

I wonder if we should remove this, it just links to the configs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It wanted to call out the "clean up the campfire" work explicitly, since it was a lot of effort.

@slim-bean slim-bean merged commit 060b6c2 into main Apr 8, 2024
12 checks passed
@slim-bean slim-bean deleted the Loki30_RN branch April 8, 2024 21:57
@grafanabot
Copy link
Collaborator

The backport to release-3.0.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-12508-to-release-3.0.x origin/release-3.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 060b6c288f2b3fd70d20e35a5f555f787ff02b92

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-12508-to-release-3.0.x
# Create the PR body template
PR_BODY=$(gh pr view 12508 --json body --template 'Backport 060b6c288f2b3fd70d20e35a5f555f787ff02b92 from #12508{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "chore: [release-3.0.x] docs: Loki 3.0 Release Notes" --body-file - --label "size/M" --label "type/docs" --label "product-approved" --label "backport" --base release-3.0.x --milestone release-3.0.x --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-12508-to-release-3.0.x

# Create a pull request where the `base` branch is `release-3.0.x` and the `compare`/`head` branch is `backport-12508-to-release-3.0.x`.

# Remove the local backport branch
git switch main
git branch -D backport-12508-to-release-3.0.x


## Bug fixes

### 3.0.0 (2024-05-08)
Copy link

Choose a reason for hiding this comment

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

We are only in April, so I think this should have been 2024-04-08?

Copy link
Contributor Author

@JStickler JStickler Apr 9, 2024

Choose a reason for hiding this comment

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

Yep that's a typo. There's a fix in #12533.

rhnasc pushed a commit to inloco/loki that referenced this pull request Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release-3.0.x backport-failed product-approved size/M type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants