Bump simple-git from 1.132.0 to 3.10.0

[dependabot]

Bumps simple-git from 1.132.0 to 3.10.0.

Release notes

Sourced from simple-git's releases.

[email protected]

Minor Changes

• 2f021e7: Support for importing as an ES module with TypeScript moduleResolution node16 or newer by adding simpleGit as a named export.

[email protected]

Minor Changes

• a0d4eb8: Branches that have been checked out as a linked work tree will now be included in the BranchSummary output, with a linkedWorkTree property set to true in the BranchSummaryBranch.

[email protected]

Minor Changes

• 25230cb: Support for additional log formats in diffSummary / log / stashList.

  Adds support for the --numstat, --name-only and --name-stat in addition to the existing --stat option.

Patch Changes

• 2cfc16f: Update CI environments to run build and test in node v18, drop node v12 now out of life.
• 13197f1: Update debug dependency to latest 4.x

[email protected]

Patch Changes

• adb4346: Resolves issue whereby renamed files no longer appear correctly in the response to git.status.

[email protected]

Minor Changes

• fa2c7f7: Enable the use of types when loading with module-resolution

Patch Changes

• 3805f6b: Timeout plugin no longer keeps short lived processes alive until timeout is hit

[email protected]

Minor Changes

• f2fc5c9: Show full commit hash in a CommitResult, prior to this change git.commit would result in a partial hash in the commit property if core.abbrev is unset or has a value under 40. Following this change the commit property will contain the full commit hash.

Patch Changes

• c4a2a13: chore(deps): bump minimist from 1.2.5 to 1.2.6

[email protected]

Minor Changes

• 2040de6: Resolves potential command injection vulnerability by preventing use of --upload-pack in git.clone

... (truncated)

Changelog

Sourced from simple-git's changelog.

3.10.0

Minor Changes

• 2f021e7: Support for importing as an ES module with TypeScript moduleResolution node16 or newer by adding simpleGit as a named export.

3.9.0

Minor Changes

• a0d4eb8: Branches that have been checked out as a linked work tree will now be included in the BranchSummary output, with a linkedWorkTree property set to true in the BranchSummaryBranch.

3.8.0

Minor Changes

• 25230cb: Support for additional log formats in diffSummary / log / stashList.

  Adds support for the --numstat, --name-only and --name-stat in addition to the existing --stat option.

Patch Changes

• 2cfc16f: Update CI environments to run build and test in node v18, drop node v12 now out of life.
• 13197f1: Update debug dependency to latest 4.x

3.7.1

Patch Changes

• adb4346: Resolves issue whereby renamed files no longer appear correctly in the response to git.status.

3.7.0

Minor Changes

• fa2c7f7: Enable the use of types when loading with module-resolution

Patch Changes

• 3805f6b: Timeout plugin no longer keeps short lived processes alive until timeout is hit

3.6.0

Minor Changes

• f2fc5c9: Show full commit hash in a CommitResult, prior to this change git.commit would result in a partial hash in the commit property if core.abbrev is unset or has a value under 40. Following this change the commit property will contain the full commit hash.

Patch Changes

... (truncated)

Commits

• 61d4ee0 Version Packages
• 2f021e7 Update documentation for importing best-practice.
• aef5f67 To enable support for ES modules in TypeScript >=4.7 (enabled with module a...
• aa8b573 Version Packages
• 43834a7 Fix test
• a0d4eb8 Branches that have been checked out as a [linked work tree](https://git-scm.c...
• e207ed5 Version Packages
• 13197f1 Update Lerna and Debug dependencies (#810)
• 28dd23b Update readme for git.diffSummary / git.stashList
• fd29242 Add integration tests for use of log formats in git.log and unit/integratio...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[secure-code-warrior-for-github]

Micro-Learning Topic: OS command injection (Detected by phrase)

Matched on "command injection"

What is this? (2min video)

In many situations, applications will rely on OS provided functions, scripts, macros and utilities instead of reimplementing them in code. While functions would typically be accessed through a native interface library, the remaining three OS provided features will normally be invoked via the command line or launched as a process. If unsafe inputs are used to construct commands or arguments, it may allow arbitrary OS operations to be performed that can compromise the server.

Try this challenge in Secure Code Warrior

[dependabot]

Superseded by #313.