Andreas/wekan
1
0
Fork 0
mirror of https://github.com/wekan/wekan.git synced 2026-02-26 01:44:07 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Record FullCalendar post-Meteor-3.0 upgrade guidance in migration guide

Browse source
This commit is contained in:
Harry Adel 2026-02-24 23:14:27 +02:00
parent d25da91e0b
commit 2fe490ec3d
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
METEOR3_MIGRATION.md
View file

@ -185,3 +185,19 @@ Key files involved in the async migration:
| `server/publications/*.js` | Meteor publications |
| `server/rulesHelper.js` | Rule trigger/action evaluation |
| `server/cronMigrationManager.js` | Cron-based migration jobs |
---
## 10. FullCalendar Versioning Note (Post-3.0 Follow-Up)
`wekan-fullcalendar` is currently migrated from legacy Meteor package globals to npm-based **FullCalendar 5.11.5** to keep Meteor 2.16 and 3.0 dual compatibility stable.
**Why pinned for now:**
- Avoids introducing additional breaking changes during core Meteor async migration.
- Keeps compatibility with current Blaze/jQuery-era integration points while removing `momentjs:moment` Meteor package dependency.
**After Meteor 3.0 lands (recommended follow-up):**
1. Re-evaluate upgrading FullCalendar to latest stable major.
2. Re-test plugin API differences (especially view names, callback signatures, locale/time formatting, CSS entry points).
3. Verify Node/runtime compatibility and bundle behavior under Meteor 3's final toolchain.
4. Keep migration isolated in a dedicated PR (separate from async data-layer work) to reduce rollback risk.