The calendar is now a widget type of its own rather than a custom widget bundled with Grist, and existing calendar pages move to it automatically. […] GRIST_SKIP_BUNDLED_WIDGETS no longer does anything (#2457)
What does it mean it concrete terms?
For self-hosted instances, if we use customized forks of the grist-widgets repository (for e.g in my case I implement this), what is the situation?
The calendar is now a built in widget, like Table or Charts. It used to be a regular custom community widget that was just bundled together with Grist installation image, but still was treated as a custom community widget. Pages that were using that “bundled” version will switch to it automatically.
Nothing changes for people who forked the widget repository and are using their own versions of calendar. It should still load normally, and from Grist perspective this is just a regular community widget taken from a gallery or an URL.
It depends on the way you made it available in your widget list once you forked it. I bet you should have 2 versions of the widget : the ‘vanilla’ bundled with regular Grist installation + yours. If you didn’t give a custom name to your custom version, it would be a good thing to do in order to clarify which one users choose.
