Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update all non-major dependencies #150

Merged
merged 1 commit into from
Jul 6, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 26, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node 16.11.41 -> 16.11.43 age adoption passing confidence
@typescript-eslint/eslint-plugin 5.29.0 -> 5.30.5 age adoption passing confidence
@typescript-eslint/parser 5.29.0 -> 5.30.5 age adoption passing confidence
eslint (source) 8.18.0 -> 8.19.0 age adoption passing confidence
eslint-plugin-prettier 4.0.0 -> 4.2.1 age adoption passing confidence
lint-staged 13.0.2 -> 13.0.3 age adoption passing confidence
pnpm (source) 7.3.0 -> 7.5.0 age adoption passing confidence
ts-node (source) 10.8.1 -> 10.8.2 age adoption passing confidence
typedoc (source) 0.22.17 -> 0.23.5 age adoption passing confidence
typedoc-plugin-rename-defaults ^0.5.1 -> ^0.6.1 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.30.5

Compare Source

Bug Fixes
  • eslint-plugin: [consistent-indexed-object-style] fix record mode fixer for generics with a default value (#​5280) (57f032c)

v5.30.4

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.30.3

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.30.2

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.30.1

Compare Source

Bug Fixes
  • eslint-plugin: [no-base-to-string] add missing apostrophe to message (#​5270) (d320174)

v5.30.0

Compare Source

Features
  • eslint-plugin: [no-shadow] add shadowed variable location to the error message (#​5183) (8ca08e9)
  • treat this in typeof this as a ThisExpression (#​4382) (b04b2ce)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.30.5

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.30.4

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.30.3

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.30.2

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.30.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.30.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

eslint/eslint

v8.19.0

Compare Source

Features
  • 7023628 feat: add importNames support for patterns in no-restricted-imports (#​16059) (Brandon Scott)
  • 472c368 feat: fix handling of blockless with statements in indent rule (#​16068) (Milos Djermanovic)
Bug Fixes
  • fc81848 fix: throw helpful exception when rule has wrong return type (#​16075) (Bryan Mishkin)
Documentation
  • 3ae0574 docs: Remove duplicate rule descriptions (#​16052) (Amaresh S M)
  • f50cf43 docs: Add base href to each page to fix relative URLs (#​16046) (Nicholas C. Zakas)
  • ae4b449 docs: make logo link clickable on small width screens (#​16058) (Milos Djermanovic)
  • 280f898 docs: use only fenced code blocks (#​16044) (Milos Djermanovic)
  • f5d63b9 docs: add listener only if element exists (#​16045) (Amaresh S M)
  • 8b639cc docs: add missing migrating-to-8.0.0 in the user guide (#​16048) (唯然)
  • b8e68c1 docs: Update release process (#​16036) (Nicholas C. Zakas)
  • 6d0cb11 docs: remove table of contents from markdown text (#​15999) (Nitin Kumar)
Chores
prettier/eslint-plugin-prettier

v4.2.1

Compare Source

Patch Changes

v4.2.0

Compare Source

Minor Changes

v4.1.0

Compare Source

okonet/lint-staged

v13.0.3

Compare Source

Bug Fixes
pnpm/pnpm

v7.5.0

Compare Source

Minor Changes

  • A new value rolling for option save-workspace-protocol. When selected, pnpm will save workspace versions using a rolling alias (e.g. "foo": "workspace:^") instead of pinning the current version number (e.g. "foo": "workspace:^1.0.0"). Usage example, in the root of your workspace, create a .npmrc with the following content:

    save-workspace-protocol=rolling
    

Patch Changes

  • pnpm remove <pkg> should not fail in a workspace that has patches #​4954
  • The hash of the patch file should be the same on both Windows and POSIX #​4961.
  • pnpm env use should throw an error on a system that use the MUSL libc.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * fix(env): throw an error on a system that uses MUSL libc by @​zkochan in https://github.com/pnpm/pnpm/pull/4958 * feat: use workspace spec alias by default in pnpm add by @​javier-garcia-meteologica in https://github.com/pnpm/pnpm/pull/4947 * fix(patch): the hash of the patch file should be the same on both Windows and POSIX by @​zkochan in https://github.com/pnpm/pnpm/pull/4969

Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0

v7.4.1

Compare Source

Patch Changes

  • pnpm install in a workspace with patches should not fail when doing partial installation #​4954.
  • Never skip lockfile resolution when the lockfile is not up-to-date and --lockfile-only is used. Even if frozen-lockfile is true #​4951.
  • Never add an empty patchedDependencies field to pnpm-lock.yaml.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * fix(lockfile): never add an empty `patchedDependencies` field to `pnpm-lock.yaml` by @​zkochan in https://github.com/pnpm/pnpm/pull/4948 * Add "refs/"+refname to resolution options by @​rotu in https://github.com/pnpm/pnpm/pull/4953 * fix: --lockfile-only in CI and with frozen-lockfile=true by @​zkochan in https://github.com/pnpm/pnpm/pull/4955 * fix: partial install in workspace with patches should not fail by @​zkochan in https://github.com/pnpm/pnpm/pull/4956 #### New Contributors * @​rotu made their first contribution in https://github.com/pnpm/pnpm/pull/4953

Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1

v7.4.0

Compare Source

Minor Changes

  • Dependencies patching is possible via the pnpm.patchedDependencies field of the package.json.
    To patch a package, the package name, exact version, and the relative path to the patch file should be specified. For instance:

    {
      "pnpm": {
        "patchedDependencies": {
          "eslint@1.0.0": "./patches/eslint@1.0.0.patch"
        }
      }
    }
  • Two new commands added: pnpm patch and pnpm patch-commit.

    pnpm patch <pkg> prepares a package for patching. For instance, if you want to patch express v1, run:

    pnpm patch express@1.0.0
    

    pnpm will create a temporary directory with express@1.0.0 that you can modify with your changes.
    Once you are read with your changes, run:

    pnpm patch-commit <path to temp folder>
    

    This will create a patch file and write it to <project>/patches/express@1.0.0.patch.
    Also, it will reference this new patch file from the patchedDependencies field in package.json:

    {
      "pnpm": {
        "patchedDependencies": {
          "express@1.0.0": "patches/express@1.0.0.patch"
        }
      }
    }
  • A new experimental command added: pnpm deploy. The deploy command takes copies a project from a workspace and installs all of its production dependencies (even if some of those dependencies are other projects from the workspace).

    For example, the new command will deploy the project named foo to the dist directory in the root of the workspace:

    pnpm --filter=foo deploy dist
    
  • package-import-method supports a new option: clone-or-copy.

  • New setting added: include-workspace-root. When it is set to true, the run, exec, add, and test commands will include the root package, when executed recursively #​4906

Patch Changes

  • Don't crash when pnpm update --interactive is cancelled with Ctrl+c.

  • The use-node-version setting should work with prerelease Node.js versions. For instance:

    use-node-version=18.0.0-rc.3
    
  • Return early when the lockfile is up-to-date.

  • Resolve native workspace path for case-insensitive file systems #​4904.

  • Don't link local dev dependencies, when prod dependencies should only be installed.

  • pnpm audit --fix should not add an override for a vulnerable package that has no fixes released.

  • Update the compatibility database.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * feat: patch package by @​zkochan in https://github.com/pnpm/pnpm/pull/4885 * feat: add `patch` and `patch-commit` commands by @​zkochan in https://github.com/pnpm/pnpm/pull/4900 * fix(env): `use-node-version` should work with prerelease versions by @​zkochan in https://github.com/pnpm/pnpm/pull/4903 * refactor: create @​pnpm/node.fetcher by @​zkochan in https://github.com/pnpm/pnpm/pull/4908 * feat(patch): update patched dependencies on install by @​zkochan in https://github.com/pnpm/pnpm/pull/4905 * fix: throw an error if not all patches were applied by @​zkochan in https://github.com/pnpm/pnpm/pull/4911 * fix: a modified patch should update the deps on install by @​zkochan in https://github.com/pnpm/pnpm/pull/4918 * fix: packages should be patched even when scripts are ignored by @​zkochan in https://github.com/pnpm/pnpm/pull/4922 * fix: patch package even if it is not in the onlyBuiltDependencies list by @​zkochan in https://github.com/pnpm/pnpm/pull/4925 * fix: respect include-workspace-root npmrc option by @​shirotech in https://github.com/pnpm/pnpm/pull/4928 * fix: install --lockfile-only should exit early by @​zkochan in https://github.com/pnpm/pnpm/pull/4932 * fix: resolve real path for case insensitive systems by @​mdogadailo in https://github.com/pnpm/pnpm/pull/4935 * feat: deploy command by @​zkochan in https://github.com/pnpm/pnpm/pull/4933 * fix: use recursive for deploy command directory creation by @​ragrag in https://github.com/pnpm/pnpm/pull/4943 * fix: don't fail when the patched pkg appears multiple times by @​zkochan in https://github.com/pnpm/pnpm/pull/4945 #### New Contributors * @​shirotech made their first contribution in https://github.com/pnpm/pnpm/pull/4928 * @​mdogadailo made their first contribution in https://github.com/pnpm/pnpm/pull/4935 * @​ragrag made their first contribution in https://github.com/pnpm/pnpm/pull/4943

Full Changelog: pnpm/pnpm@v7.3.0...v7.4.0

TypeStrong/ts-node

v10.8.2

Compare Source

Fixed

  • Revert "Use file URL for source map paths" (#​1821) @​cspotcode
    • Fixes #​1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
    • Fixes #​1797: ts-node 10.8.1 regression where breakpoints did not hit in VSCode debugging
  • Allow JSON imports in node 16.15 and up (#​1792) @​queengooborg
    • JSON imports were already supported in v17.5 and up
    • this change extends support to >=16.15.0,<17.0.0
    • These version ranges match vanilla node's support for JSON imports

https://github.com/TypeStrong/ts-node/milestone/15?closed=1

TypeStrong/TypeDoc

v0.23.5

Compare Source

Features
  • The DEBUG_SEARCH_WEIGHTS global variable can now be set on window to add search scoring information in the search results.
  • TypeDoc's icons are now available on DefaultThemeRenderContext.icons for use/modification by themes.

v0.23.4

Compare Source

Bug Fixes
  • TypeDoc no longer ignores project references if --entryPointStrategy Packages is set, #​1976.
  • Boost computations are now done when creating the search index, resulting in a smaller search.js generated file.
Features
  • The --exclude option will now be respected by --entryPointStrategy Packages and can be used to exclude package directories, #​1959.
  • TypeDoc now emits an IndexEvent on the Renderer when preparing the search index, #​1953.
  • Added new --searchInComments option to include comment text in the search index, #​1553.
    Turning this option on will increase the size of your search index, potentially by an order of magnitude.

v0.23.3

Compare Source

Bug Fixes
  • Function properties in type space will no longer be interpreted as methods, #​1637.
  • TypeDoc will no longer crash if a comment contains an empty @example tag, #​1967.
  • TypeDoc will now detect attempted inheritance from accessors and inherit from the getter or setter, #​1968.
  • intentionallyNotExported will now properly respect qualified names, #​1972.
  • Fixed missing namespace comments on export * as NS declarations, #​1973.
  • Fixed missing comments on export const x = () => 123 function variables, #​1973.
  • Exported variable functions with properties will now be converted as a function+namespace instead of a variable+namespace, #​1651.
  • Validation warnings caused by missing documentation will now be formatted like other warnings which reference a declaration.
  • TypeDoc will no longer warn if both the get and set signatures of an accessor have a comment.
Features
  • Added --htmlLang option to set the lang attribute in the generated HTML. Defaults to en, #​1951.
  • Added --basePath option to override TypeDoc's detected root directory, #​1924.
  • Added support for TypeDoc specific :getter and :setter meaning keywords in declaration references.
  • Warnings caused by comment contents will now do a better job of including the location of the text that caused the warning.

v0.23.2

Compare Source

Bug Fixes
  • Module comments will no longer be inappropriately attached to signatures, #​1962.
  • Projects with a single entry point will now parse @module comments in the entry point, #​1963.
  • Removed duplicate "in comment" warning when parsing comments, #​1964.
  • Reflections with a boost of <= 0 due to searchCategoryBoosts or searchGroupBoosts will be excluded from search.

v0.23.1

Compare Source

Bug Fixes
  • If a declaration has multiple comments associated with it, the last one should be used, #​1961.

v0.23.0

Compare Source

Breaking Changes
  • Node 12 is no longer officially supported as it has gone end of life as of 2022-04-30. It might still work, but may stop working at any time.
  • Dropped support for TypeScript before 4.6.
  • {@&#8203;link} tags in comments will now be resolved as declaration references similar to TSDoc's declaration references.
    For most cases, this will just work. See the documentation for details on how link resolution works.
  • TypeDoc will now produce warnings for bracketed links ([[ target ]]). Use {@&#8203;link target} instead. The {@&#8203;link} syntax will be recognized by TypeScript 4.3 and later and used to provide better intellisense. TypeDoc version 0.24.0 will remove support for [[ target ]] style links.
  • extends in typedoc.json is now resolved using NodeJS module resolution, so a local path must begin with ./.
  • In the JSON output for DeclarationReflections, getSignature is no longer a one-tuple.
  • In the JSON output for DeclarationReflections, setSignature is no longer a one-tuple.
  • In the JSON output for DeclarationReflections, typeParameter has been renamed to typeParameters
  • The searchGroupBoosts option must now be given the rendered group name rather than reflection kind names, and can be given custom group names.
  • @inheritDoc now follows the behavior specified by TSDoc when copying comments with a reference.
  • The gaSite option has been removed since Google Analytics now infers the site automatically, updated Google Analytics script to latest version, #​1846.
  • The hideLegend option has been removed as the default theme no longer contains a legend.
  • Comments on export declarations will only overrides comments for references and namespaces, #​1901.
  • The deprecated listInvalidSymbolLinks option has been removed. Use validation.invalidLink instead.
  • The deprecated true and false values have been removed from --emit, to migrate replace true with "both" and false with "docs" (the default).
  • Links are no longer be resolved against a global list of all symbols. See the documentation for details on link resolution.
  • The validation.invalidLink option is now on by default.
  • reflection.decorates, reflection.decorators, and their corresponding interfaces have been removed as no code in TypeDoc used them.
  • The shape of the Comment class has changed significantly to support multiple tag kinds.
  • Listeners to Converter.EVENT_CREATE_TYPE_PARAMETER and Converter.EVENT_CREATE_DECLARATION will now never be passed a ts.Node as their third argument.
  • Constant variables which are interpreted as functions will no longer have the ReflectionFlag.Const flag set.
  • reflection.defaultValue is no longer set for enum members. The same information is available on reflection.type with more precision.
  • Removed deprecated removeReaderByName, addDeclarations and removeDeclarationByName methods on Options.
  • Removed ProjectReflection.directory, it was unused by TypeDoc and not properly tested.
  • Removed ProjectReflection.files, this was an internal cache that should not have been exposed, and shouldn't have existed in the first place, since removing it made TypeDoc faster.
  • Removed ReflectionGroup.kind since groups can now be created with the @group tag.
  • Removed ReflectionKind.Event, the @event tag is now an alias for @group Events. Note: This changes the value of ReflectionKind.Reference from 16777216 to 8388608.
  • Themes are now set on the document element rather than on body, #​1706.
Features
  • TypeDoc now supports the @group tag to group reflections in a page. If no @group tag is specified, reflections will be grouped according to their kind, #​1652.

  • TypeDoc will now search for typedoc.js(on) in the .config folder in the current working directory.

  • Entry point strategies Resolve and Expand may now specify globs, #​1926.

  • typedoc.json now supports comments like tsconfig.json.

  • TypeDoc will now read the blockTags, inlineTags, and modifierTags out of tsdoc.json in the same directory as tsconfig.json if it exists.
    It is recommended to add "extends": ["typedoc/tsdoc.json"], which defines TypeDoc specific tags to your tsdoc.json if you create one.

  • If an exported symbol has multiple declarations, TypeDoc will now check all appropriate declarations for comments, and warn if more than one declaration contains a comment, #​1855.

  • Improved support for JSDoc style @example tags. If the tag content does not include a code block, TypeDoc now follows VSCode's behavior of treating the entire block as a code block, #​135.

  • TypeDoc will now render members marked with @deprecated with a line through their name, #​1381.

  • Added new commentStyle option which can be used to control what comments TypeDoc will parse.

    Value Behavior
    JSDoc Use block comments starting with /**
    Block Use all block comments
    Line Use // comments
    All Use both block and line comments
  • TypeDoc will now warn if part of a comment will be overwritten due to use of @inheritDoc instead of silently dropping part of the comment.

  • Added support for inline @inheritDoc tags, #​1480.

  • It is now possible to link directly to a specific overload, #​1326.

  • The JSON output will now include URLs to the file on the remote repository if possible.

  • Added a new visibilityFilters option which controls the available filters on a page.

  • TypeDoc will now try to place block elements on a new line in HTML output, resulting in less overwhelming diffs when rebuilding docs, #​1923.

  • Added blockTags, inlineTags, modifierTags to control which tags TypeDoc will allow when parsing comments.
    If a tag not in in one of these options is encountered, TypeDoc will produce a warning and use context clues to determine how to parse the tag.

Bug Fixes
  • Fixed off by one error in warnings for types referenced but not included in the documentation.
  • TypeDoc will no longer render a Type Parameters heading if there are no type parameters in some cases.
  • Improved source location detection for constructors.
  • Improved comment discovery on destructured exported functions, #​1770.
  • Links which refer to members within a reference reflection will now correctly resolve to the referenced reflection's member, #​1770.
  • Correctly detect optional parameters in JavaScript projects using JSDoc, #​1804.
  • Fixed identical anchor links for reflections with the same name, #​1845.
  • TypeDoc will now automatically inherit documentation from classes implements by other interfaces/classes.
  • Fixed @inheritDoc on accessors, #​1927.
  • JS exports defined as exports.foo = ... will now be converted as variables rather than properties.
  • searchCategoryBoosts are now correctly computed for all categories, #​1960.
  • The excludeNotDocumented option will no longer hide a module if it has a documentation comment, #​1948.
  • Prevent --excludeNotDocumented from hiding properties of type literals (a in function fn(p: { a: string })), #​1752.
  • Allow cts and mts extensions in packages resolution mode, #​1952.
  • Corrected schema generation for https://typedoc.org/schema.json
Thanks!

v0.22.18 (2022-06-25)

Features
  • Relaxed restrictions on @enum style enums to also permit non-literal strings and numbers, #​1956.
Bug Fixes
  • searchGroupBoosts was only computing the boost for the first reflection in a group, #​1958.
Thanks!

v0.22.17 (2022-06-01)

Features
  • Added support for documenting a module's global declarations as its exports if it contains no real exports.
Bug Fixes
  • Restore support for TS 4.0 through 4.5, #​1945.

v0.22.16 (2022-05-30)

Features
  • Added support for TypeScript 4.7, #​1935.
  • Support enum-like objects with numeric literal values tagged with @enum, #​1918.
  • Enum member reflections will now have their type set to either a LiteralType with a string or numeric value or an IntrinsicType with type number, #​1942.
    Using defaultValue on EnumMember reflections is now deprecated, and will be broken in 0.23.
Bug Fixes
  • Fixed invalid type output in some uncommon edge cases, TypeDoc also now renders fewer superfluous parenthesis when creating types.
  • TypeDoc is now more consistent about ordering with enum-value-ascending or enum-value-descending sort strategies in mixed string/number enums.
Thanks!

v0.22.15 (2022-04-10)

Features
  • Classes which are abstract and enums which are const will now be indicated in their rendered documentation, #​1874.
  • Added a new option compilerOptions, which can be used to override compiler options read from tsconfig.json, #​1891.
  • Added new render hooks: content.begin, content.end, navigation.begin, navigation.end
Bug Fixes
  • TypeDoc will now warn if a project name/version cannot be inferred from a package.json file rather than using undefined, #​1907.
Thanks!

v0.22.14 (2022-04-07)

Bug Fixes
  • Fixed missing comments on @enum style enum members defined in declaration files, #​1880.
  • Fixed --validation.notDocumented warnings for functions/methods/type aliases, #​1895, #​1898.
  • Search results will no longer include random items when the search bar is empty, #​1881.
  • Comments on overloaded constructors will now be detected in the same way that overloaded functions/methods are.
  • Fixed removeReflection not completely removing reflections from the project, #​1898.
  • Fixed @hidden / @ignore / @exclude comments on default exports with no associated variable, #​1903.
  • makeRecursiveVisitor will now correctly call the intersection callback, #​1910.
Thanks!

v0.22.13 (2022-03-06)

Features
  • Add support for TypeScript 4.6, #​1877.
  • Support copying @param comments for nested members that target union and intersection types, #​1876.
Bug Fixes
  • Fixed validation for --requiredToBeDocumented option, #​1872.
  • Fixed missing this parameters in documentation for some functions, #​1875.

v0.22.12 (2022-02-20)

Features
  • Added --validation.notDocumented option to warn on items that are not documented, #​1817.
Bug Fixes
  • Fixed const variables not properly marked as const, #​1866.
Thanks!

v0.22.11 (2022-01-18)

Features
  • Added new cname option for GitHub Pages custom domain support, #​1803.
  • ReferenceTypes which reference an external symbol will now include qualifiedName and package in their serialized JSON.
  • Added clickable anchor link for member titles, #​1842.
Bug Fixes
  • Fixed line height of h1 and h2 elements being too low, #​1796.
  • Code blocks in the light theme will no longer have the same background as the rest of the page, #​1836.
  • Symbol names passed to addUnknownSymbolResolver will now be correctly given the qualified name to the symbol being referenced, #​1832.
  • The search index will now be written as JSON, reducing load times for large projects, #​1825.
Thanks!

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

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

@changeset-bot
Copy link

changeset-bot bot commented Jun 26, 2022

⚠️ No Changeset found

Latest commit: 3974c46

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 20 times, most recently from 20ae7e4 to c46598a Compare July 3, 2022 13:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c46598a to 439318f Compare July 4, 2022 18:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 439318f to 3974c46 Compare July 5, 2022 21:36
@zaida04 zaida04 merged commit 6eeb1c7 into main Jul 6, 2022
@zaida04 zaida04 deleted the renovate/all-minor-patch branch July 6, 2022 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant