chore(deps-dev): bump @grafana/tsconfig from 1.2.0-rc1 to 2.0.1 #102
Conversation
Bumps [@grafana/tsconfig](https://github.com/grafana/plugin-tools/tree/HEAD/packages/tsconfig) from 1.2.0-rc1 to 2.0.1. - [Release notes](https://github.com/grafana/plugin-tools/releases) - [Changelog](https://github.com/grafana/plugin-tools/blob/main/CHANGELOG.md) - [Commits](https://github.com/grafana/plugin-tools/commits/@grafana/tsconfig@2.0.1/packages/tsconfig) --- updated-dependencies: - dependency-name: "@grafana/tsconfig" dependency-version: 2.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
Levitate is-compatible report: 🔍 Resolving @grafana/data@latest... 🔬 Checking compatibility between ./src/module.ts and @grafana/data@12.3.0... 🔬 Checking compatibility between ./src/module.ts and @grafana/ui@12.3.0... 🔬 Checking compatibility between ./src/module.ts and @grafana/runtime@12.3.0... Comparing @grafana/runtime@12.2.1 to @grafana/runtime@12.3.0 INCOMPATIBILITIES (3) 🔬 Checking compatibility between ./src/module.ts and @grafana/schema@12.3.0... 🔬 Checking compatibility between ./src/module.ts and @grafana/e2e-selectors@12.3.0... 🔬 Checking compatibility between ./src/module.ts and @grafana/experimental@2.1.6... ./src/module.ts is not fully compatible with @grafana/data,@grafana/ui,@grafana/runtime,@grafana/schema,@grafana/e2e-selectors,@grafana/experimental If you think the compatibility issues are not a problem (e.g. only type changes), it is adviced to update the target list of packages to their latest version in your project. |
Bumps @grafana/tsconfig from 1.2.0-rc1 to 2.0.1.
Release notes
Sourced from
@grafana/tsconfig's releases.Changelog
Sourced from
@grafana/tsconfig's changelog.... (truncated)
Commits
Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@grafana/tsconfigsince your current version.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)