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 go-plugin dep #20966

Merged
merged 3 commits into from
Aug 22, 2023
Merged

Bump go-plugin dep #20966

merged 3 commits into from
Aug 22, 2023

Conversation

evan2645
Copy link
Contributor

@evan2645 evan2645 commented Jun 2, 2023

Bumps the go-plugin package to pick up a bugfix that broke our project on Windows. Our project uses the Vault SDK and we'd like to bump to the latest, but can't until the Windows bugfix is picked up.

I had some issues with the go tooling, it wasn't quite happy with the current state of go.mod. Forcing an upgrade of go-plugin to the same version that currently appears in go.mod resulted in many other dependency changes, so I resorted to editing manually ... what am I doing wrong?

Thanks in advance for your help here

@hashicorp-cla
Copy link

hashicorp-cla commented Jun 2, 2023

CLA assistant check
All committers have signed the CLA.

Bumps the go-plugin package to pick up a bugfix that broke our project
on Windows. Our project uses the Vault SDK and we'd like to bump to the
latest, but can't until the Windows bugfix is picked up.

I had some issues with the go tooling, it wasn't quite happy with the
current state of go.mod. Forcing an upgrade of go-plugin to the same
version that currently appears in go.mod resulted in many other
dependency changes, so I resorted to editing manually ... what am I
doing wrong?

Thanks in advance for your help here
@maxb
Copy link
Contributor

maxb commented Jun 3, 2023

Our project uses the Vault SDK and we'd like to bump to the latest, but can't until the Windows bugfix is picked up.

Unless I've misunderstood how Go works, you should be able to just ask Go to use the new go-plugin version in your own project (go get github.com/hashicorp/go-plugin) right now, to pick up the bugfix, without needing another release of vault/sdk first.

I had some issues with the go tooling, it wasn't quite happy with the current state of go.mod.

There does appear to be something weird going on, I ended up opening golang/go#60588.

Separately, please run go mod tidy in the root directory of your branch and commit the result. You need to do this because the root directory of the Vault project includes the sdk via a local directory replace:

vault/go.mod

Line 23 in 155003a

replace github.com/hashicorp/vault/sdk => ./sdk

and you have changed the sdk's go.mod.

@evan2645
Copy link
Contributor Author

you should be able to just ask Go to use the new go-plugin version in your own project right now, to pick up the bugfix

Ah awesome, thank you!

Separately, please run go mod tidy in the root directory of your branch and commit the result. You need to do this because the root directory of the Vault project includes the sdk via a local directory replace

Sure, just pushed that up

Copy link
Contributor

@tomhjp tomhjp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for raising! I added a changelog, LGTM

@tomhjp tomhjp enabled auto-merge (squash) August 22, 2023 15:00
@tomhjp tomhjp merged commit 1c4d3dd into hashicorp:main Aug 22, 2023
54 of 55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants