Uh oh!
There was an error while loading. Please reload this page.
Add new org to Weaver instrumentation - #9195
Conversation
There was a problem hiding this comment.
Thanks for opening this PR @majk-p! From what I've gathered by locally testing, I think some additional changes will be necessary in order to support TypeLevel releases too, as currently the instrumentation will break with them. Will get back to you as soon as I take a look 👍
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
daniel-mohedano
commented
Jul 24, 2025
@majk-p the PR looks good to go! With the changes to the instrumentation the new typelevel versions will be supported moving forward. Could you please rebase and sign your initial commit to the PR in order to unblock the check? |
majk-p
commented
Jul 24, 2025
All done now! I accidentally overwrote your changes with the rebase, but cherry-picked them from #9235, I hope it's fine |
ad7bf27 to
45f4161Compare
What Does This Do
Updates Weaver instrumentation to take into account changes to the organization following the recent migration
Motivation
Weaver has been migrated (typelevel/tsc#114) from disneystreaming (https://github.com/disneystreaming/weaver-test) to typelevel (https://github.com/typelevel/weaver-test) organization. It has also got version updates in the meantime.
Additional Notes
Passing CI on #9235
Contributor Checklist
type:and (comp:orinst:) labels in addition to any usefull labelsclose,fixor any linking keywords when referencing an issue.Use
solvesinstead, and assign the PR milestone to the issueJira ticket: [PROJ-IDENT]