(chore): Bump @redhat-cloud-services/frontend-components-notifications from 4.1.1 to 4.1.2 in the ci-dependencies group #4158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the ci-dependencies group with 1 update: [@redhat-cloud-services/frontend-components-notifications](https://github.com/RedHatInsights/frontend-components). Updates `@redhat-cloud-services/frontend-components-notifications` from 4.1.1 to 4.1.2 - [Release notes](https://github.com/RedHatInsights/frontend-components/releases) - [Changelog](https://github.com/RedHatInsights/frontend-components/blob/master/CHANGELOG.md) - [Commits](https://github.com/RedHatInsights/frontend-components/compare/@redhat-cloud-services/frontend-components-notifications-4.1.1...@redhat-cloud-services/frontend-components-notifications-4.1.2) --- updated-dependencies: - dependency-name: "@redhat-cloud-services/frontend-components-notifications" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: ci-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4158 +/- ##
=======================================
Coverage 64.82% 64.82%
=======================================
Files 518 518
Lines 10201 10201
Branches 2405 2405
=======================================
Hits 6613 6613
Misses 3319 3319
Partials 269 269 ☔ View full report in Codecov by Sentry. |
|
Looks like @redhat-cloud-services/frontend-components-notifications is updatable in another way, so this is no longer needed. |
dependabot
bot
deleted the
dependabot_npm_and_yarn_main_ci-dependencies-3d21514091
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the ci-dependencies group with 1 update: @redhat-cloud-services/frontend-components-notifications.
Updates
@redhat-cloud-services/frontend-components-notificationsfrom 4.1.1 to 4.1.2Commits
d09a859chore: bump@redhat-cloud-services/frontend-components-notificationsto 4.1.2...814241achore: bump@redhat-cloud-services/frontend-components-configto 6.3.5 [skip ci]0dfc8fbchore: bump@redhat-cloud-services/frontend-componentsto 5.0.2 [skip ci]64f2226Merge pull request #2126 from florkbr/fix-fec-config-utils-missing-templateef6d77cfix(fec): fix missing template.json when running fec dev37dc2eachore: bump@redhat-cloud-services/eslint-config-redhat-cloud-servicesto 2.0...d42bd84chore: bump@redhat-cloud-services/frontend-components-configto 6.3.4 [skip ci]7ad06fdchore: bump@redhat-cloud-services/tsc-transform-importsto 1.0.21 [skip ci]c526d2echore: bump@redhat-cloud-services/frontend-components-config-utilitiesto 4....77f76c8chore: bump@redhat-cloud-services/frontend-components-utilitiesto 5.0.4 [sk...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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions