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

Goodbye vendor dir #1059

Merged
merged 1 commit into from Jun 6, 2022
Merged

Goodbye vendor dir #1059

merged 1 commit into from Jun 6, 2022

Conversation

kanata2
Copy link
Member

@kanata2 kanata2 commented Apr 22, 2022

Remove vendor directory

@kanata2 kanata2 added this to the v0.11.0 milestone Apr 23, 2022
Copy link

@obalunenko obalunenko left a comment

Choose a reason for hiding this comment

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

Prefer to keep vednor directory committed to have reproducible builds and be save from disappearing of libraries from GitHub.
https://blog.boot.dev/golang/should-you-commit-the-vendor-folder-in-go/

@kanata2
Copy link
Member Author

kanata2 commented Apr 24, 2022

My understanding is that Go modules should remain cached in the module proxy even if a repository is deleted.

@obalunenko
Copy link

@kanata2 Unfortunately proxy servers that're not self hosted cannot provide any guarantee that they will not lose module.
Anyway this topic was always controversial. Just interesting article to read https://www.ardanlabs.com/blog/2020/04/modules-06-vendoring.html

Copy link
Contributor

@zchee zchee left a comment

Choose a reason for hiding this comment

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

I think self hosted proxy server haven't good SLO than hosted by Google Go team. so LGTM.

@kanata2 kanata2 merged commit 9fd6da5 into master Jun 6, 2022
@kanata2 kanata2 deleted the goodbye-vendor branch June 6, 2022 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Review done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants