search

AdamOswald / tes

2 stars 1 forks source link

Update devops-actions/json-to-file action to v1.0.1 #109

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
devops-actions/json-to-file action patch v1.0.0 -> v1.0.1

Release Notes

devops-actions/json-to-file ### [`v1.0.1`](https://togithub.com/devops-actions/json-to-file/releases/tag/v1.0.1) [Compare Source](https://togithub.com/devops-actions/json-to-file/compare/v1.0.0...v1.0.1) Bump dependency versions #### What's Changed - Bump eslint from 8.13.0 to 8.14.0 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/16](https://togithub.com/devops-actions/json-to-file/pull/16) - Bump eslint-plugin-jest from 26.1.4 to 26.1.5 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/15](https://togithub.com/devops-actions/json-to-file/pull/15) - Bump minimatch from 3.0.4 to 3.1.2 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/114](https://togithub.com/devops-actions/json-to-file/pull/114) - Bump [@​types/node](https://togithub.com/types/node) from 17.0.25 to 18.11.13 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/130](https://togithub.com/devops-actions/json-to-file/pull/130) - Bump [@​actions/core](https://togithub.com/actions/core) from 1.6.0 to 1.10.0 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/97](https://togithub.com/devops-actions/json-to-file/pull/97) - Bump [@​typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) from 5.20.0 to 5.46.1 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/132](https://togithub.com/devops-actions/json-to-file/pull/132) - Bump github/codeql-action from 1 to 2 in /.github/workflows by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/121](https://togithub.com/devops-actions/json-to-file/pull/121) - Bump actions/setup-node from 3.1.1 to 3.5.1 in /.github/workflows by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/120](https://togithub.com/devops-actions/json-to-file/pull/120) - Bump typescript from 4.6.3 to 4.9.4 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/129](https://togithub.com/devops-actions/json-to-file/pull/129) - Bump [@​typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) from 5.20.0 to 5.46.1 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/devops-actions/json-to-file/pull/131](https://togithub.com/devops-actions/json-to-file/pull/131) **Full Changelog**: https://github.com/devops-actions/json-to-file/compare/v1.0.0...v1.0.1

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Mend Renovate. View repository job log here.

viezly[bot] commented 1 year ago

Pull request by bot. No need to analyze

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

Unable to locate .performanceTestingBot config file

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: .yml : +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.

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.

  2. Complete the activities.

    Action: Complete If you want to rebase/retry this PR, check this box

    If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

difflens[bot] commented 1 year ago

View changes in DiffLens