Skip to content
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

Bump github.com/shirou/gopsutil from 2.20.7+incompatible to 2.20.8+incompatible in /instrumentation/host #331

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 6, 2020

Bumps github.com/shirou/gopsutil from 2.20.7+incompatible to 2.20.8+incompatible.

Commits
  • 9aa2bee Merge pull request #933 from Lomanic/openbsd-host-mem-process-types
  • 84afaae [host][mem][process][openbsd] Add 386 const and types definitions
  • 7f588ac Merge pull request #930 from tklauser/openbsd-uvmpexp
  • e643eae Merge pull request #931 from tklauser/openbsd-mem-test-fix
  • 62354ea Fix TestVirtual_memory on OpenBSD
  • aacbba2 Use unix.SysctlUvmexp on OpenBSD
  • c466301 Merge pull request #923 from disconnect3d/patch-2
  • d9f9a85 Merge pull request #924 from nightmared/fix-utf16-windows
  • 5c1a9e7 net_linux.go: decode port as 16-bit uint
  • 04a6f81 fix an invalid shift in windows processes name UTF16 conversion
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/shirou/gopsutil](https://github.com/shirou/gopsutil) from 2.20.7+incompatible to 2.20.8+incompatible.
- [Release notes](https://github.com/shirou/gopsutil/releases)
- [Commits](shirou/gopsutil@v2.20.7...v2.20.8)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Sep 6, 2020
@MrAlias MrAlias merged commit de985d7 into master Sep 8, 2020
@MrAlias MrAlias deleted the dependabot/go_modules/instrumentation/host/github.com/shirou/gopsutil-2.20.8incompatible branch September 8, 2020 17:35
plantfansam referenced this pull request in plantfansam/opentelemetry-go-contrib Mar 18, 2022
The `go.opentelemetry.io/otel/exporter/trace/jaeger` package was
mistakenly released with a `v1.0.0` tag instead of `v0.1.0`. This
resulted in all subsequent releases not becoming the default latest,
meaning that `go get`s pulled in the incompatible `v0.1.0` release of
that package when pulling in more recent packages from other otel
packages. Renaming the `exporter` directory to `exporters` fixes this
issue by consequentially renaming the package.

Additionally, this action also renames *all* exporters. This is
understood to be a disruptive action to existing users as they will need
to update any dependencies they currently have on our exporters.
However, it was decided to take this action regardless. The need to
resolve the existing issue explained above is highly important, and
given the Alpha state of this project these kinds of breaking changes
should be expected (though not without reason).

Resolves #331

Co-authored-by: Rahul Patel <rghetia@yahoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant