build(deps): bump gridstack from 12.6.0 to 13.2.0

[dependabot]

Bumps gridstack from 12.6.0 to 13.2.0.

Release notes

Sourced from gridstack's releases.

v13.2.0

• feat: #701 removed printMode as we support much better printing now that doesn't compromise.
• feat: #3362 added PrintOptions.mode for app custom settings
• fix: #3357 (react): drop type assertions on useGridStack add/remove helpers - thank you YOUNGHO8762
• fix: #3358 (react): use wrapper widget types in registry callbacks - thank you YOUNGHO8762
• fix: #3360 better north and west resize handles - thank you Ryan Peterson

v13.1.2

• reg: #3340 regression: strict mode (v13.0.0) fails columnWidth without .breakpoints - thank you Daniel Cohen Gindi

v13.1.1

• feat: #3336 printMode?: 'flow' | 'exact' to support 2 very differenrt options due to browser bug. uddated demos to showcase one vs the other (and mode toggle)

v13.1.0

• feat: #701 major printing support for grids using PrintOptions (pageBreak, hide, orientation, ...)
• feat: #3329 DOM matches the visual order when widgets are moved around (accessibility tabbing, regular printing)

v13.0.1

• fix: #3325 preinstall script
• fix: #3324 vue files missing from package

v13.0.0

• NEW: React wrapper: re-did to follow the Angular pattern (drag&Drop between grid doesn't destroy content), events, lazyLoad support, fix memory leak, empty content, etc...
• NEW: Vue wrapper: brand new wrapper follow same pattern as well
• break: #3310 Angular wrapper using component+props (instead of selector+input)
• feat: #662 added grid-lines.html demo (just CSS)
• fix: #3154 Esc key doesn't restore subgrid
• fix: #3231 drag broken in Firefox 147.0.4+ and Chrome 144+ due to navigator.maxTouchPoints > 0 now returning true on desktop (macOS trackpad)
• fix: #3291 flicker nested grid demo when dragging between sub-grids
• fix: #3085 Changing rows after init relays out if smaller
• fix: #2823 Scrollbar appears prevents onChange being called
• fix: #2948 dynamically created nested grid disappeared when dragging out
• fix: #3269 cleanup old rtl residue - thank you Daniel Cohen Gindi
• fix: #3270 dragging item from outside doesn't allow swap (weird change is layout especially when you move out as it doesn't restore)
• fix: #2950 Angular: now support signal inputs (ng14.1+) like name = input<string>()

Changelog

Sourced from gridstack's changelog.

13.2.0 (2026-08-19)

• feat: #701 removed printMode as we support much better printing now that doesn't compromise.
• feat: #3362 added PrintOptions.mode for app custom settings
• fix: #3357 (react): drop type assertions on useGridStack add/remove helpers - thank you YOUNGHO8762
• fix: #3358 (react): use wrapper widget types in registry callbacks - thank you YOUNGHO8762
• fix: #3360 better north and west resize handles - thank you Ryan Peterson

13.1.2 (2026-07-26)

• reg: #3340 regression: strict mode (v13.0.0) fails columnWidth without .breakpoints - thank you Daniel Cohen Gindi

13.1.1 (2026-07-25)

• feat: #3336 printMode?: 'flow' | 'exact' to support 2 very differenrt options due to browser bug. uddated demos to showcase one vs the other (and mode toggle)

13.1.0 (2026-07-22)

• feat: #701 major printing support for grids using PrintOptions (pageBreak, hide, orientation, ...)
• feat: #3329 DOM matches the visual order when widgets are moved around (accessibility tabbing, regular printing)

13.0.2 (2026-07-26)

• reg: #3340 regression: strict mode (v13.0.0) fails columnWidth without .breakpoints - thank you Daniel Cohen Gindi

13.0.1 (2026-07-22)

• fix: #3325 preinstall script
• fix: #3324 vue files missing from package

13.0.0 (2026-07-18)

• NEW: react wrapper: re-did to follow the Angular pattern (drag&Drop between grid doesn't destroy content), events, lazyLoad support, fix memory leak, empty content, etc...
• NEW: vue wrapper: brand new wrapper follow same pattern as well
• break: #3310 Angular wrapper using component+props (instead of selector+input)
• feat: #662 added grid-lines.html demo (just CSS)
• fix: #3154 Esc key doesn't restore subgrid
• fix: #3231 drag broken in Firefox 147.0.4+ and Chrome 144+ due to navigator.maxTouchPoints > 0 now returning true on desktop (macOS trackpad)
• fix: #3291 flicker nested grid demo when dragging between sub-grids
• fix: #3085 Changing rows after init relays out if smaller
• fix: #2823 Scrollbar appears prevents onChange being called
• fix: #2948 dynamically created nested grid disappeared when dragging out
• fix: #3269 cleanup old rtl residue - thank you Daniel Cohen Gindi
• fix: #3270 dragging item from outside doesn't allow swap (weird change is layout especially when you move out as it doesn't restore)
• fix: #2950 Angular: now support signal inputs (ng14.1+) like name = input<string>()

Commits

• 26a49d6 Merge pull request #3364 from adumesny/master
• 256f696 vue doc
• ebe7d85 refactor(vue): use wrapper widget types in registry callbacks
• 4f04cee refactor(vue): drop type assertions on useGridStack add/remove helpers
• 99897ca v13.2.0
• 5955aeb Merge pull request #3363 from adumesny/master
• e276485 PrintOptions.mode, gs-print-show
• 3cf8dd4 Merge pull request #3362 from adumesny/master
• 04d362c more fix #3360 N/W resizing
• 00d4496 Merge pull request #3360 from ryanpetebyte/master
• Additional commits viewable in compare view

[rubenvdlinde]

Closing: this bump cannot be installed, verified rather than assumed.

Applying gridstack@^13.2.0 to this app's own package.json and asking npm to resolve the tree fails:

peer node-polyfill-webpack-plugin@"4.0.0" from @nextcloud/webpack-vue-config@6.3.2

The package is peered by something else this app depends on, at a range the new major does not satisfy — so npm rejects the entire tree, not just this package. Merging it would leave npm ci unable to run, and every frontend job fails at install before reporting anything about the code.

That is not hypothetical. Eight apps were in exactly that state tonight — planninq, filinq, stackiq, integriq, dossiq, pipelinq, decidiq and hermiq — from majors of this same family landing without the peers that must move with them. Each one had every frontend check failing at install while looking like ordinary CI redness.

This is not a judgement that the upgrade is undesirable. It is that the upgrade is not available yet: it needs the packages that peer it to move first, and then the whole set adopted together. Dependabot will reopen it when that changes.

Measured across the fleet: of 51 npm majors tested this way, 24 could not install and 27 could.

[dependabot]

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 @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.