Skip to content

docs: State which versions we do maintain #4085

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

Merged
merged 1 commit into from
Apr 9, 2025

Conversation

simonswine
Copy link
Contributor

@simonswine simonswine commented Apr 8, 2025

As pointed out on the community slack, we don't document what releases are supported.

As pointed out on the community slack, we don't document what releases
are supported.
@simonswine simonswine force-pushed the 20250408_maintained-pyroscope branch from eb3c70a to 26c12ad Compare April 8, 2025 10:44
@simonswine simonswine changed the title 20250408 maintained pyroscope docs: State which versions we do maintain Apr 8, 2025
@simonswine simonswine marked this pull request as ready for review April 8, 2025 10:49
@simonswine simonswine requested review from a team as code owners April 8, 2025 10:49
Copy link
Contributor

@marcsanmi marcsanmi left a comment

Choose a reason for hiding this comment

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

LGTM

@simonswine simonswine added backport release/v1.12 This label will backport a merged PR to the release/v1.12 branch backport release/v1.13 This label will backport a merged PR to the release/v1.13 branch type/docs Improvements for doc docs. Used by Docs team for project management labels Apr 8, 2025
Copy link
Contributor

github-actions bot commented Apr 8, 2025

Hello @simonswine!
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!

Copy link
Contributor

github-actions bot commented Apr 8, 2025

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

Copy link
Contributor

github-actions bot commented Apr 8, 2025

Hello @simonswine!
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!

@simonswine simonswine merged commit 1f168a7 into grafana:main Apr 9, 2025
23 checks passed
github-actions bot pushed a commit that referenced this pull request Apr 9, 2025
As pointed out on the community slack, we don't document what releases
are supported.

(cherry picked from commit 1f168a7)
github-actions bot pushed a commit that referenced this pull request Apr 9, 2025
As pointed out on the community slack, we don't document what releases
are supported.

(cherry picked from commit 1f168a7)
marcsanmi pushed a commit that referenced this pull request Apr 9, 2025
As pointed out on the community slack, we don't document what releases
are supported.

(cherry picked from commit 1f168a7)

Co-authored-by: Christian Simon <[email protected]>
marcsanmi pushed a commit that referenced this pull request Apr 9, 2025
As pointed out on the community slack, we don't document what releases
are supported.

(cherry picked from commit 1f168a7)

Co-authored-by: Christian Simon <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/v1.12 This label will backport a merged PR to the release/v1.12 branch backport release/v1.13 This label will backport a merged PR to the release/v1.13 branch type/docs Improvements for doc docs. Used by Docs team for project management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants