chore(deps): bump fullcalendar from 3.10.5 to 6.1.21#1351
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(deps): bump fullcalendar from 3.10.5 to 6.1.21#1351dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dj4oC
reviewed
Jul 9, 2026
dj4oC
left a comment
Contributor
There was a problem hiding this comment.
- Security: no findings (dependency bump only, fullcalendar 3.10.5 → 6.1.20)
- Stability: repo CI is currently red on this branch —
Commits / Validate semantic commitsandbuild / Buildboth fail on the head commit;JS Unitpasses. This is a major fullcalendar version bump (3.x→6.x) which historically carries breaking API changes, so the build failure needs investigation before merge, not just a commit-message fix. - Performance: no findings
- Test coverage: n/a (dependency bump, no app code touched)
- TODOs found: 0
- Dependency touched: yes — fullcalendar (MIT), major version jump 3→6
- CI status: failing (Commits, build); JS Unit green
Verdict
Not mergeable as-is — CI red on build and commit-message validation, and a major version jump this large needs a human to verify the calendar UI still renders/functions before merge. Leaving as informational; not approving.
🤖 Automated review by Claude Code (security · stability · performance · coverage)
Generated by Claude Code
Member
|
@dependabot rebase |
Bumps [fullcalendar](https://github.com/fullcalendar/fullcalendar/tree/HEAD/bundle) from 3.10.5 to 6.1.21. - [Release notes](https://github.com/fullcalendar/fullcalendar/releases) - [Changelog](https://github.com/fullcalendar/fullcalendar/blob/v6.1.21/CHANGELOG.md) - [Commits](https://github.com/fullcalendar/fullcalendar/commits/v6.1.21/bundle) --- updated-dependencies: - dependency-name: fullcalendar dependency-version: 6.1.20 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
28353ac to
38dd0dc
Compare
Member
|
Holding: CI is failing (not a rebase conflict). Failing check(s): JS Unit / Javascript Unit. A rebase won't fix this — needs a human/upstream fix. |
This file contains hidden or 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
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 fullcalendar from 3.10.5 to 6.1.21.
Release notes
Sourced from fullcalendar's releases.
... (truncated)
Changelog
Sourced from fullcalendar's changelog.
... (truncated)
Commits
9e0ea05bumpb0c1d6cRELEASING: Releasing 33 package(s)09b96afbump version87ca245bump0800158bump70fa10aRELEASING: Releasing 33 package(s)1ad00a7RELEASING: Releasing 33 package(s)5988b09RELEASING: Releasing 31 package(s)030ce6dRELEASING: Releasing 31 package(s)b802cbetest case for event dnd on stacked calendarsMost Recent Ignore Conditions Applied to This Pull Request