-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
CI: Depend On Releases #7131
Comments
@Stebalien : thanks for creating. This came out of some recent issues right? If easily available, link to them for context. |
Nothing filed in issues. Commits we depend on that aren't on master:
We also have a lot of dependencies on master commits. I'm suggesting that we make sure we depend on releases, not just master, because it's strictly easier to check/maintain:
|
List of Lotus dependencies that aren't of a released version.
|
In light of #12467, I elaborated in the issue description. I did this because this an action item I think maintainers should take on as a preventative measure. @Stebalien's original issue description:
|
Note: The idea was to require released versions for dependencies with released versions.
And two pre-release packages:
|
Proposed IPDX SoW that we've been discussing (thanks @galargh):
@galargh: one point of clarification: this will only flag on new or changed dependencies (regardless if they are direct or transitive). Basically I want to make sure that we don’t encumber future PRs with “sins of the past”. I just want to make sure we hold the line and don’t repeat the sins of the past, but it's a separate effort to clean up past sins. |
One option is to have a separate config file (json) for listing all the "excepted" dependencies. |
Done Criteria
A CI check catches if go.mod is being updated with any non-released version. This includes checking direct and transitive dependencies. There should be a way for maintainers to override this check (e.g., PR label or code comment that links to explanation).
Why Important
User/Customer
Notes
The text was updated successfully, but these errors were encountered: