chore(deps): bump hyfi from 1.32.1 to 1.33.0

[dependabot[bot]]

Bumps hyfi from 1.32.1 to 1.33.0.

Release notes

Sourced from hyfi's releases.

v1.33.0

Feature

• tests: Add user_config_path in initialize method and compose workflow test configuration (8518905)
• HyFI: Add plugin and path options to main class (86b6e64)
• config: Add new optional parameters in GlobalConfig class, reinitialize with new parameters in GlobalConfig class (60945c9)
• core: Add reinitialize method to GlobalHyFIConfig class (531de35)

v1.32.2

Fix

• hyfi: Improved about method in GlobalConfig class; remove conditional in application name method (c4af792)

Changelog

Sourced from hyfi's changelog.

v1.33.0 (2023-08-25)

Feature

• tests: Add user_config_path in initialize method and compose workflow test configuration (8518905)
• HyFI: Add plugin and path options to main class (86b6e64)
• config: Add new optional parameters in GlobalConfig class, reinitialize with new parameters in GlobalConfig class (60945c9)
• core: Add reinitialize method to GlobalHyFIConfig class (531de35)

v1.32.2 (2023-08-25)

Fix

• hyfi: Improved about method in GlobalConfig class; remove conditional in application name method (c4af792)

Commits

• 16e1fe8 chore(release): :rocket: 1.33.0 [skip ci]
• a52432d Merge pull request #242 from entelecheia/entelecheia/issue234
• 8518905 feat(tests): add user_config_path in initialize method and compose workflow t...
• 86b6e64 feat(HyFI): add plugin and path options to main class
• 60945c9 feat(config): add new optional parameters in GlobalConfig class, reinitialize...
• 531de35 feat(core): add reinitialize method to GlobalHyFIConfig class
• 2bdb198 chore(release): :rocket: 1.32.2 [skip ci]
• 669b14a Merge pull request #240 from entelecheia/entelecheia/issue239
• c4af792 fix(hyfi): improved about method in GlobalConfig class; remove conditional in...
• See full diff 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

[dependabot[bot]]

The following labels could not be found: :game_die: dependencies, :robot: bot.

[pull-request-quantifier-deprecated[bot]]

This PR has 4 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 : +2 -2 Percentile : 1.6% Total files changed: 1 Change summary by file extension: .lock : +2 -2 ``` > 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.

[dependabot[bot]]

Superseded by #64.