hack: add script to sync common dependiences with core to the version core uses #335
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.
Description
Dependencies getting out of sync can be problematic given that xk6-disruptor is typically built together with k6 core. We've always anticipated
goja
to be a potential dependency to watch for, but as #330 proves, others may also cause problems as well.This PR adds a (go) script that looks for overlapping dependencies with k6 core which do not match the version used in core. Those dependencies are logged to
stderr
, andgo get
commands are generated to stdout to download the version k6 core is using.That way, by running
go run ./hack/depsync > /dev/null
, one can easily get a list of unsynced dependencies. By runninggo run ./hack/depsync | bash
, dependencies are synced to core.Checklist:
make lint
) and all checks pass.make test
) and all tests pass.make e2e-xxx
foragent
,disruptors
,kubernetes
orcluster
related changes)