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

[DO NOT MERGE] Tooling for auditing dependencies #2054

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ni-jfitzger
Copy link
Collaborator

TODO: Check the above box with an 'x' indicating you've read and followed CONTRIBUTING.md.

TODO: Check the above box with an 'x' if considered if there were any and then documented client facing changes in CHANGELOG.md. Strike through if this is not a relevant client facing change.

  • I've added tests applicable for this pull request

TODO: Check the above box with an 'x' indicating you have considered and added any applicable system or unit tests. Strike through if you considered and decided additional tests were not warranted.

What does this Pull Request accomplish?

For now, I found this useful to help audit what versions of our deps are being used for releasing, a process which is currently handled on a local developer machine.

Ultimately, I think we want to instead lock down our deps and run the release process from a github-runner for better traceability, security, reproduceability, etc.

List issues fixed by this Pull Request below, if any.

TODO: List of issues.

  • Fix #xxx
  • Fix #yyy

What testing has been done?

TODO: Detail what testing has been done to ensure this submission meets requirements.

@ni-jfitzger ni-jfitzger changed the title DO NOT SUBMIT: Tooling for auditing dependencies [DO NOT MERGE] Tooling for auditing dependencies Apr 24, 2024
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.

1 participant