GitKraken interactive rebase signature preservation for GPG-signed commits

GitKraken provides a visual interactive rebase interface for reordering, squashing, dropping or editing commits by drag-and-drop in the commit graph.

For repositories that use GPG-signed commits, history rewriting invalidates signatures because Git does not automatically re-sign rewritten commits. GitKraken documentation describes GPG signing support for new commits, but it does not explicitly describe signature handling during interactive rebase operations. The expected behavior for signature preservation and any built-in re-sign option is unclear.

Does GitKraken automatically preserve or re-sign GPG signatures after an interactive rebase? Is signature loss the documented default for history rewrites in current releases? How is signature preservation for rebased commits documented, if at all?