search

AdamOswald / tes

2 stars 1 forks source link

[Snyk] Upgrade grunt-contrib-sass from 0.9.2 to 2.0.0 #18

Closed snyk-bot closed 1 year ago

snyk-bot commented 1 year ago

Snyk has created this PR to upgrade grunt-contrib-sass from 0.9.2 to 2.0.0.

merge advice :information_source: 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.

Release notes
Package name: grunt-contrib-sass from grunt-contrib-sass GitHub release notes
Commit messages
Package name: grunt-contrib-sass
  • 000f6d5 2.0.0
  • ede3adf Merge pull request #259 from gruntjs/upt-deps-3
  • 0630c1e v2.0.0 changelog
  • 4274480 Bump some dependencies
  • 44b0860 Merge pull request #258 from gruntjs/dependabot/npm_and_yarn/lodash-4.17.20
  • 6f07e49 Merge pull request #257 from gruntjs/dependabot/npm_and_yarn/underscore.string-3.3.5
  • 6d8c550 Bump lodash from 4.17.15 to 4.17.20
  • c09853e Bump underscore.string from 3.3.4 to 3.3.5
  • b67504c Merge pull request #256 from gruntjs/update-ci
  • 9da4296 Update CI targets
  • 3602226 Merge pull request #252 from gruntjs/dependabot/npm_and_yarn/lodash-4.17.15
  • 409b019 Bump lodash from 4.17.10 to 4.17.15
  • e1f8664 Merge pull request #248 from gruntjs/dev
  • f98c38c Update all deps, drop Node.js < 6 support, and update links.
  • 4d56455 Upgrade grunt and devDeps to 1.0.
  • be8205a Update AppVeyor config.
  • 519d4d2 Fix tests on Windows.
  • fe81ce8 Update CHANGELOG.
  • fe1308a Add Appveyor for Windows testing.
  • eb295c5 Update dependencies.
  • d60bcf5 v1.0.0
  • 2c2379f CI: Remove node.js '0.12' and add '5'.
  • b8da420 Update docs.
  • 45a389f JSHint: Check subfolders too.
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

performance-testing-bot[bot] commented 1 year ago

Unable to locate .performanceTestingBot config file

mezidia-inspector[bot] commented 1 year ago

Nice to meet you, @snyk-bot. Thank you for creating a pull request. There are some tasks for you:

To close issue send comment "close", to reopen - "reopen", to merge - "merge"

pull-request-quantifier-deprecated[bot] commented 1 year ago

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](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

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 detected. - 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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

difflens[bot] commented 1 year ago

View changes in DiffLens

guide-bot[bot] commented 1 year ago

Thanks for opening this Pull Request! We need you to:

  1. Fill out the description.

    Action: Edit description and replace <!- ... --> with actual values.

viezly[bot] commented 1 year ago

Changes preview:

Legend:

👀 Review pull request on Viezly

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **PHP Composer** - Path: [.github/workflows/php.yml](.github/workflows/php.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958075 - Run number: 145 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build (3.8)** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Install dependencies** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **undefined** - Path: [undefined](undefined) - Workflow URL: undefined - Run number: undefined - Status: ✅ undefined - Conclusion: ❌ undefined
Job - Name: **undefined** - Status: ✅ undefined - Conclusion: ❌ undefined
Step - Name: **undefined** - Status: ✅ undefined - Conclusion: ❌ undefined

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Symfony** - Path: [.github/workflows/symfony.yml](.github/workflows/symfony.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958078 - Run number: 157 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **symfony-tests** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Install Dependencies** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Java CI with Maven** - Path: [.github/workflows/maven.yml](.github/workflows/maven.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958073 - Run number: 154 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **pysa** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Run Pysa** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Go** - Path: [.github/workflows/go.yml](.github/workflows/go.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958065 - Run number: 148 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Build** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **SonarCloud analysis** - Path: [.github/workflows/sonarcloud.yml](.github/workflows/sonarcloud.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958070 - Run number: 71 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **configure** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **C/C++ CI** - Path: [.github/workflows/c-cpp.yml](.github/workflows/c-cpp.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958079 - Run number: 153 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **configure** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **.NET** - Path: [.github/workflows/dotnet.yml](.github/workflows/dotnet.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958082 - Run number: 147 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Restore dependencies** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **.NET Core Desktop** - Path: [.github/workflows/dotnet-desktop.yml](.github/workflows/dotnet-desktop.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958064 - Run number: 149 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **A job to run a Nexploit scan** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Start Nexploit Scan 🏁** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Node.js CI** - Path: [.github/workflows/node.js.yml](.github/workflows/node.js.yml) - Workflow URL: https://github.com/AdamOswald/Ai-test/actions/runs/3236455552 - Run number: 1162 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Restore NuGet packages** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **NodeJS with Grunt** - Path: [.github/workflows/npm-grunt.yml](.github/workflows/npm-grunt.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958085 - Run number: 73 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build (16.x)** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Build** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **iOS starter workflow** - Path: [.github/workflows/ios.yml](.github/workflows/ios.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958092 - Run number: 155 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **Build and Test default scheme using any available iPhone simulator** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Set Default Scheme** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Xcode - Build and Analyze** - Path: [.github/workflows/objective-c-xcode.yml](.github/workflows/objective-c-xcode.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958077 - Run number: 156 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **Build and analyse default scheme using xcodebuild command** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Set Default Scheme** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **NodeJS with Webpack** - Path: [.github/workflows/webpack.yml](.github/workflows/webpack.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958074 - Run number: 144 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build (16.x)** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Build** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Swift** - Path: [.github/workflows/swift.yml](.github/workflows/swift.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958063 - Run number: 137 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Build** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Java CI with Gradle** - Path: [.github/workflows/gradle.yml](.github/workflows/gradle.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958080 - Run number: 161 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Build with Gradle** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Python application** - Path: [.github/workflows/python-app.yml](.github/workflows/python-app.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958084 - Run number: 139 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Lint with flake8** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Node.js CI** - Path: [.github/workflows/node.js.yml](.github/workflows/node.js.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958061 - Run number: 142 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **Run (ubuntu-latest)** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Set Node.js 16.x** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **Python package** - Path: [.github/workflows/python-package.yml](.github/workflows/python-package.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958076 - Run number: 141 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **build (3.10)** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **Lint with flake8** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!

workflow-reporter[bot] commented 1 year ago

Hi @snyk-bot,

Details:

Workflow - Name: **CodeQL** - Path: [.github/workflows/codeql-analysis.yml](.github/workflows/codeql-analysis.yml) - Workflow URL: https://github.com/AdamOswald/tes/actions/runs/3240958130 - Run number: 78 - Status: ✅ completed - Conclusion: ❌ failure
Job - Name: **Setup PyPy pypy-2.7-v7.3.4rc1 macos-latest** - Status: ✅ completed - Conclusion: ❌ failure
Step - Name: **setup-python pypy-2.7-v7.3.4rc1** - Status: ✅ completed - Conclusion: ❌ failure

Report:

No Report Message!