Skip to content

Update Pyroscope and Tempo instrumentation library versions #1929

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

andrewslotin
Copy link
Contributor

@andrewslotin andrewslotin commented Apr 17, 2025

Do not merge until grafana/jslib.k6.io#154 is deployed.

What?

Updated Tempo and Pyroscope instrumentation examples to use the latest versions of both libraries.

Checklist

  • I have used a meaningful title for the PR.
  • I have described the changes I've made in the "What?" section above.
  • I have performed a self-review of my changes.
  • I have run the npm start command locally and verified that the changes look good.
  • I have made my changes in the docs/sources/k6/next folder of the documentation.
  • I have reflected my changes in the docs/sources/k6/v{most_recent_release} folder of the documentation.
  • I have reflected my changes in the relevant folders of the two previous k6 versions of the documentation (if still applicable to previous versions).

Related PR(s)/Issue(s)

Implementation PR: grafana/jslib.k6.io#154

@andrewslotin andrewslotin added the Area: OSS Content Improvements or additions to community/oss documentation label Apr 17, 2025
@andrewslotin andrewslotin requested review from heitortsergent and a team as code owners April 17, 2025 16:21
@andrewslotin andrewslotin requested review from inancgumus and joanlopez and removed request for a team April 17, 2025 16:21
@andrewslotin
Copy link
Contributor Author

@heitortsergent, the build is failing because new versions are not released yet. This PR should be merged only after grafana/jslib.k6.io#154 is deployed.

@heitortsergent
Copy link
Collaborator

@andrewslotin what do you think of adding a variable for the library versions, so we can just update it in one place whenever we need to? We're doing this for the aws library, we have a variable defined here: https://github.com/grafana/k6-docs/blob/main/docs/sources/k6/_index.md?plain=1#L22

@heitortsergent heitortsergent self-assigned this Apr 17, 2025
@andrewslotin
Copy link
Contributor Author

@heitortsergent I think this is a good idea!

@heitortsergent
Copy link
Collaborator

@andrewslotin do you want me to make the changes and commit to this PR? 🤓

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: OSS Content Improvements or additions to community/oss documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants