Bump @fullcalendar/timegrid from 5.7.2 to 5.8.0 #3238
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [@fullcalendar/timegrid](https://github.com/fullcalendar/fullcalendar) from 5.7.2 to 5.8.0. - [Release notes](https://github.com/fullcalendar/fullcalendar/releases) - [Changelog](https://github.com/fullcalendar/fullcalendar/blob/master/CHANGELOG.md) - [Commits](fullcalendar/fullcalendar@v5.7.2...v5.8.0) --- updated-dependencies: - dependency-name: "@fullcalendar/timegrid" dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov Report
@@ Coverage Diff @@
## master #3238 +/- ##
=========================================
Coverage 28.86% 28.86%
Complexity 121 121
=========================================
Files 157 157
Lines 5731 5731
Branches 841 841
=========================================
Hits 1654 1654
Misses 4077 4077
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
|
Superseded by #3254. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/fullcalendar/timegrid-5.8.0
branch
Bumps @fullcalendar/timegrid from 5.7.2 to 5.8.0.
Release notes
Sourced from
@fullcalendar/timegrid's releases.Changelog
Sourced from
@fullcalendar/timegrid's changelog.Commits
90da1d2lint fix4a3c9e7bump versionf844093upgrade tslib84b33eafix event positioning problemsb594fd0fix problem with gotoDate and navigating a view that already has currentDate ...e455ff8fix prev nav bug50dafc0update subreposc5813ebbugfix. lint fixes8e56095separate seg hierarchy/web from event-placement files9025f16normalize event placement typesDependabot 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 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)