Add release notes for 7.2.2 and 7.2.3 Both shipped without wiki coverage — they carried the Serializable fixes for session passivation (#239, #240). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FvqEaaPLypCvjJrjCsdLjK
Retire the MCP server page The FullCalendar Vaadin MCP server has been shut down and removed from the repository: its npm dependency tree produced a constant stream of security advisories, and it only re-served this wiki in machine-readable form. MCP-Server keeps its URL as a tombstone — it is linked from users' MCP configs and from the Vaadin Directory — and now explains the shutdown and points at the wiki pages to use instead. Removes the sidebar entry and the Getting-Started pointer; the Features entry links to the tombstone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FvqEaaPLypCvjJrjCsdLjK
Document 6.5.1 RRule serialization fixes (#237) Mirror of the 7.2.1 release notes on the 6.x line: - Release-notes-6.5: new top section for 6.5.1 covering the exrule crash, DTSTART auto-inject, the excludeRules(ofRaw) guard, and the toJson() return-type change. 6.5.0 content demoted to a dedicated ## section. - Release-notes index: split the 6.5.x block into 6.5.1 and 6.5.0. - Features: extended the "Broken in …" and "(x.y.z+)" markers to cover both the 7.2.1 and the 6.5.1 fixes.
Document 7.2.1 RRule serialization fixes (#237) - Release-notes-7.2: new top section for 7.2.1 covering the exrule crash, DTSTART auto-inject, the excludeRules(ofRaw) guard, and the toJson() return-type change. - Release-notes index: 7.2.x bullet entry for 7.2.1. - Features: added Exclusion rules row (excludeRules) and a short note on the DTSTART fallback.
Release 6.5: drop -wip suffix from release notes + migration guide Renames Release-notes-6.5-wip.md → Release-notes-6.5.md and Migration-guide-6.4-to-6.5-wip.md → Migration-guide-6.4-to-6.5.md. Strips the "work in progress" banners and index markers, and updates the internal cross-links between the two pages.
Release 7.2: drop -wip suffix from release notes + migration guide Renames Release-notes-7.2-wip.md → Release-notes-7.2.md and Migration-guide-7.1-to-7.2-wip.md → Migration-guide-7.1-to-7.2.md. Strips the "work in progress" banner from both pages, removes the "(work in progress)" markers on Migration-guides.md and Release-notes.md, and updates all internal links on this wiki (Samples, FullCalendar-Examples, Release-notes-6.5-wip, the pages themselves) to point at the released URLs. 6.5 rename follows when that release ships.
Reviewer pass on 7.2 / 6.5 docs + new v6→v7 guide - Migration-guide-6.x-to-7.x: reworded the "prerequisite" line that contradicted the guide's own purpose, softened the "cross-pair jumps" sentence, and flagged BusinessHours + theme-variant rename as 7.0 changes (they predate 7.2 but are documented here for v6 readers). - Promoted the `### Highlights` heading in both release notes to H2 so the top-level hierarchy is consistent; same treatment for the "6.5 or 7.x?" decision block. - Converted the last stray relative wiki link in Release-notes.md to a full GitHub URL (project convention for external viewers). - Fleshed out the 7.1 → 7.2 bullet on Migration-guides.md with the full change set; added a matching summary line to the 6.4 → 6.5 bullet and reworded the "step one only" phrasing on 6.3 → 6.4. Review feedback dismissed as false positive: the @Deprecated(since = ...) asymmetry between 7.2 and 6.5 is deliberate in the source (6.x source uses plain @Deprecated throughout, 7.x uses since = "7.2.0") and the release notes accurately reflect each branch.
some text rework
Consolidate v6→v7 migration into a single page with version mapping The two previous v6-to-v7 pages overlapped and made users pick between "6.3 → 7.1" and "6.4 → 7.1" without making clear which v7.x target corresponds to their current v6.x. Replace both with one generalized Migration-guide-6.x-to-7.x page that leads with a version-mapping table (6.4 ↔ 7.1, 6.5 ↔ 7.2, and space for future pairs) and then covers the universal platform switch (Jackson 3, BusinessHours, theme variant, CSS tokens, Aura). Users on 6.3 or older are routed through 6.3 → 6.4 first. Deletes Migration-guide-6.3-to-7.1.md and Migration-guide-6.4-to-7.1.md; their content is absorbed into the new page.
Clarify auto-revert docs after end-user review (#225) Migration guides (7.1→7.2, 6.4→6.5) now include an explicit "upgrade impact" call-out for drop/resize listeners that did not call applyChangesOnEntry() on the previous version — those listeners will now trigger the revert animation. Release notes rephrase the isChangesApplied() reference with context on when it's useful. Rolling-back section points forward to the impact note so readers see which of the two default-on changes needs the most attention.
Release notes 6.5: document the editable=true addon default (#212) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Release notes: document the editable=true addon default (#212) Add a note to the #212 section explaining why the addon deliberately diverges from FC JS's native `editable: false` default. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Rewrite 6.5 #231 release note to reflect proper fix (batched writes) Match the 7.2 rewrite: the root-cause fix is batching all server-side resource writes through beforeClientResponse. API signatures unchanged; the only user-visible difference is that the client is notified at the end of the current request instead of immediately after each call. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Rewrite #231 release note to reflect proper fix (batched resource writes) The fix changed from a bounded TS-side retry loop on scrollgrid settling to batching all server-side resource writes through beforeClientResponse so only one callJsFunction per op-type fires per request. The race goes away at its source instead of being recovered from after the fact. - Problem statement: re-framed around "N addResource calls → N JS round-trips → FC can't settle" instead of the scrollgrid-internals explanation. - Fix statement: new batching pipeline with collapse rules for same-request add+remove, remove+re-add, update-after-add, and removeAll-supersedes-all. API signatures unchanged. - Dropped the sizingRetryMaxWaitMs / sizingRetryIntervalMs element properties — they were escape hatches for the retry loop and are no longer present. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Review-pass polish: backport framing, 6.5-vs-7.x decision, platform - Release-notes-6.5-wip: reframe platform line as "designed for teams who want 7.2 features without the V25 / Java 21 upgrade". Add a "6.5 or 7.x?" decision section so users landing on the page can decide without leaving it. Platform version loosened to "Vaadin 24.9.x" so it matches what's actually on the 6.x line (reduced from 24.10 in a 6.4 patch). - Migration-guide-6.4-to-6.5-wip: add "What 6.5 is" paragraph calling it explicitly a backport, so readers who skip the release notes don't lose the framing. Fix the withInitialEntries migration-table row — the snippet used `calendar` without declaring it; now shows two lines with the declaration. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add 6.5 release notes + migration guide (wip) 6.5 is the backport of 7.2's feature set to the v6.x line (Vaadin 24.9.8, Java 17, elemental JSON). Release-notes-6.5-wip and Migration-guide-6.4-to-6.5-wip are structured to match their 7.2 counterparts; the index pages Release-notes.md and Migration-guides.md gain 6.5 entries. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Release notes + migration polish: highlights, rollback, external events - Release-notes-7.2-wip: add "Highlights" bullet list below the platform paragraph so skim-readers see the top-billed changes at a glance. - Release-notes-7.2-wip: clarify that ExternalEntryDroppedEvent / ExternalEntryResizedEvent do NOT participate in auto-revert (by design — external drops create new entries; the handler owns the decision). - Release-notes-7.2-wip: fix undeclared `id` variable in the updateResource example (use "room-1"). - Migration-guide-7.1-to-7.2-wip: add "Rolling back to 7.1 behaviour" section showing the one-liner opt-outs for both default-on 7.2 features (auto-provide entry IDs + auto-revert). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Release notes: mention Option.INITIAL_VIEW; tighten migration caveat - Release-notes-7.2-wip: add paragraph under FullCalendarBuilder section explaining Option.INITIAL_VIEW and that the builder now uses it too. - Migration-guide: clarify that `view.getClientSideValue()` works on any CalendarView (typically a CalendarViewImpl enum constant), resolving the minor mismatch between the table row and the caveat example. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Migration guide: use Option.INITIAL_VIEW instead of attach-listener (#232) Replace the builder-migration table's attach-listener workaround with the clean setOption(Option.INITIAL_VIEW, ...) call. Verified with an e2e probe that FullCalendar 6.1.20 renders both the initial view and its entries correctly on first attach (plus scheduler resource view with resources and entries). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Wiki polish for 7.2 release - Fix broken GitHub URL slugs: `vaadin_fullcalendar` (underscore) → `vaadin-fullcalendar` (hyphen) across all wiki pages. - Add banner on Samples.md and FullCalendar-Examples.md clarifying that pre-7.2 API in the examples (`FullCalendarBuilder.create()`, `event.createCopyBasedOnChanges()`) still works but has deprecated replacements — link to the migration guide. - Migration-guide-7.1-to-7.2-wip: add platform statement (FC JS / Vaadin / Java unchanged), spell out the single binary-compat caveat (Entry.setEditable descriptor change for #212), and glossary for "start segment" / `applyChangesOnEntry()`. - Release-notes-7.2-wip: add platform line at the top. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Rename auto-assign-entry-ids docs to auto-provide-entry-id-on-client (#202) Matches the renamed FullCalendar setter. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Document DemoDialog resource selection (#164) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Document Delta.getYears/getMonths deprecation (#191) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Document EntryDataEvent.getChangesAsEntry rename Adds release-notes and migration-guide entries for the createCopyBasedOnChanges → getChangesAsEntry rename. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Document auto-assign entry IDs (#202) Adds release-notes-7.2-wip and migration-guide-7.1-to-7.2-wip entries for the default DOM id assignment on rendered entries. Release-notes index gets the one-liner. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Document per-entry editable fix for 7.2 (#212) Add bug-fix section to Release-notes-7.2-wip explaining why calendar-level editable:false was being ignored, how the fix works at the serialization level, and the binary-compat note for the setEditable method signature change. Add bullet to Release-notes index.
Document scheduler timeline sizing fix for 7.2 (#231) Add bug-fix section to Release-notes-7.2-wip with background, fix description and the property-override escape hatch. Add bullet to the Release-notes index.
Document updateResource extended props fix for 7.2 (#230) Add bug-fix entry to Release-notes-7.2-wip with a short before/after example. Add corresponding bullet to the Release-notes index.
Document FullCalendarBuilder deprecation for 7.2 (#232) - New page Migration-guide-7.1-to-7.2-wip with full migration table (Builder calls → direct constructor + setOption), before/after example, and caveats for the two non-trivial replacements (InMemoryEntryProvider cast assumption, attach-listener for initialView). - Release-notes-7.2-wip: added "Deprecated: FullCalendarBuilder" section with short before/after example and link to the migration guide. - Migration-guides index: new "Upgrading within 7.x" section with the 7.1 → 7.2 entry. - Release-notes index: added builder-deprecation bullet under 7.2.x. Emphasizes that deprecation does not mean imminent removal — the class continues to work throughout 7.x. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Consolidate migration guides, add 7.2 WIP release notes (#234) Split the inline Migration-guides page into six standalone detail pages — one per version jump — and turn the main Migration-guides page into a pure index. - Migration-guide-3.x-to-4.0 - Migration-guide-4.0-to-4.1 - Migration-guide-4.1-to-6.0 - Migration-guide-6.3-to-7.1 - Migration-guide-6.4-to-7.1 Migration-guide-6.3-to-6.4 already existed standalone and stays. Add Release-notes-7.2-wip as the in-progress release-notes page for the upcoming 7.2 release, with the auto-revert section (#225). Add index entry to Release-notes with a "(work in progress)" marker per the -wip convention. Fix stale event-class-name reference in 6.3 → 7.1 guide (NavLinkDayClickedEvent does not exist; use EntryDragStartEvent / ExternalEntryDroppedEvent which do). Minor polish in 3.x → 4.0 guide (typo, consistent anchor links). Part of the wiki-as-single-source initiative — the main repo's docs/ folder is being removed in a follow-up commit on master. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>