feat: split telemetry from @dagger.io/dagger #11684
Open
+1,827
−942
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Move telemetry logic into
@dagger.io/telemetryand import it in@dagger.io/daggerThe release process is decouple from
@dagger.io/dagger, there's a new check in the ts SDK that verify that we correctly bump the package version when we update that package so later we can automatically release it.When we build a dagger engine, we use the local telemetry package so we are always up to date and it makes tests always using the latest changes.
List of changes
@dagger.io/telemetrypackage.sdk-typescript-devto verify we correctly bump the version.@dagger.io/telemetryin@dagger.io/dagger.