-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: replace lockfile detection with
phylum status
The changes here are centered around the use of `phylum status` for project and dependency file information. The `phylum status` command for printing project and lockfile details was added in CLI v5.1.0 but the fix to search for manifests' lockfiles in parent, rather than child directories was added in CLI v5.6.0, making this the new minimum CLI version required for new and existing installs. Now that both lockfiles and manifests are supported, the "lockfile" language has been changed to the more general term "dependency file" where it is externally visible (e.g., log and help output) but kept as "lockfile" internally (e.g., code/variable names). It is still not clear what to do for the situations where dependency files require more context for lockfile generation than just the previous/base version of that same file. Actions taken include: * Use `phylum status` for common tasks instead of custom code to * look for dependency files in `.phylum_project` * detect the dependency files present * acquire the initial project file backup * Downgrade the minimum CLI version required for new/existing installs * Remove the straddling code for `phylum analyze` command usage * No longer needed now that the minimum CLI version is > v5.3.1-rc1 * Remove the CINone pre-requisite * Needing to run from the root of a git repository is no longer true * Provide warning message when attempting to create a Phylum project outside the top-level of a `git` repository * Update externally visible `lockfile` language throughout * Use `dependency file` instead, to represent lockfiles and manifests * Format and refactor throughout * Improve log messages Closes #244
- Loading branch information
Showing
9 changed files
with
119 additions
and
187 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters