[Snyk] Upgrade gulp-inject from 1.3.1 to 5.0.5

[snyk-bot]

Snyk has created this PR to upgrade gulp-inject from 1.3.1 to 5.0.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

Warning: This is a major version upgrade, and may be a breaking change.

• The recommended version is 19 versions ahead of your current version.
• The recommended version was released 2 years ago, on 2019-12-29.

Release notes

Package name: gulp-inject

• 5.0.5 - 2019-12-29
  

  5.0.5 (2019-12-29)

  Bug Fixes

  • fix xo linting errors after dependencies update (d3c4ae0)
• 5.0.4 - 2019-07-23
  

  5.0.4 (2019-07-23)

  Bug Fixes

  • update group-array and other dependencies, fixes #261 (8a434d0)
• 5.0.3 - 2019-07-17
  

  5.0.3 (2019-07-17)

  Bug Fixes

  • disable linting for one specific line (58808fa)
  • update dependencies (e393f98)
• 5.0.2 - 2018-11-27
  

  5.0.2 (2018-11-27)

  Bug Fixes

  • pin event-stream to v3.3.4 (59bf9c6)
• 5.0.1 - 2018-11-27
  

  5.0.1 (2018-11-27)

  Bug Fixes

  • update dependencies (822873f)
• 5.0.0 - 2018-11-15
  

  5.0.0 (2018-11-15)

  Build System

  • upgrade husky config, (97b1f16)

  BREAKING CHANGES

  • drop node4 support
• 4.3.2 - 2018-03-29
  

  4.3.2 (2018-03-29)

  Bug Fixes

  • update twig support from github.com//pull/129 (831d4b0)
• 4.3.1 - 2018-02-23
  

  4.3.1 (2018-02-23)

  Bug Fixes

  • drop dependency on deprecated gulp-util (#236) (3a3b465), closes #235
• 4.3.0 - 2017-09-15
  

  4.3.0 (2017-09-15)

  Features

  • add semantic-release (b37939e)
• 4.2.1 - 2017-09-15
• 4.2.0 - 2016-12-20
• 4.1.0 - 2016-05-18
• 4.0.0 - 2016-03-18
• 3.0.0 - 2015-09-24
• 2.2.0 - 2015-09-14
• 2.1.0 - 2015-09-14
• 2.0.1 - 2015-09-14
• 2.0.0 - 2015-09-14
• 1.5.0 - 2015-07-21
• 1.3.1 - 2015-06-11

from gulp-inject GitHub release notes

Commit messages

Package name: gulp-inject

• d3c4ae0 fix: fix xo linting errors after dependencies update
• ebe9e83 build: add intellij files to gitignore
• 5ca790f build(deps): bump handlebars from 4.1.2 to 4.5.3 (#266)
• 4aa65e1 build(deps): bump npm from 6.10.1 to 6.13.4 (#265)
• 61773be build(deps): bump eslint-utils from 1.3.1 to 1.4.3 (#264)
• 58949a6 Merge pull request #262 from klei/fix_issue_261
• 8a434d0 fix: update group-array and other dependencies, fixes #261
• 58808fa fix: disable linting for one specific line
• 151115c build: remove node6 due to EndOfLife
• e393f98 fix: update dependencies
• a7249f1 Merge pull request #258 from britishgas-engineering/master
• 1c5ba66 Update package.json
• ed91930 build: update dependencies, move event-stream to devDeps
• 59bf9c6 fix: pin event-stream to v3.3.4
• 822873f fix: update dependencies
• d370592 chore: remove old changelog (#248)
• 97b1f16 build: upgrade husky config,
• ff8f9b0 fix: update dependencies (#245)
• 831d4b0 fix: update twig support from github.com/Error on missing inject tags, Twig support klei/gulp-inject#129
• f69bc70 Merge pull request #197 from gligoran/master
• 3a3b465 fix: drop dependency on deprecated `gulp-util` (#236)
• cf66da0 chore: upgrade semantic-release
• 390979d chore: fix whitespace
• 424556f chore: only run release script on the "master" branch

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[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: 1

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

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.