# Migrating to 2026 April

## Introduction

This page discusses breaking changes and other considerations when migrating from `2026 March` to `2026 April`.

## Upgrading Gum Tool

{% tabs %}
{% tab title="Windows" %}
To upgrade the Gum tool:

1. Download Gum.zip from the release on Github:\
   <https://github.com/vchelaru/Gum/releases/tag/Release_May_02_2026>
2. Delete the old tool from your machine
3. Unzip the gum tool to the same location as to not break any file associations
   {% endtab %}

{% tab title="Linux" %}
Run the upgrade `gum upgrade` or `~/bin/gum upgrade`
{% endtab %}
{% endtabs %}

## Upgrading Runtime

Upgrade your Gum NuGet packages to version **2026.4.2.1**. For more information, see the NuGet packages for your particular platform:

* MonoGame - <https://www.nuget.org/packages/Gum.MonoGame/>
* KNI - <https://www.nuget.org/packages/Gum.KNI/>
* FNA - <https://www.nuget.org/packages/Gum.FNA/>
* raylib - <https://www.nuget.org/packages/Gum.raylib>
* .NET MAUI - <https://www.nuget.org/packages/Gum.SkiaSharp.Maui>
* SkiaSharp - <https://www.nuget.org/packages/Gum.SkiaSharp/>

If using GumCommon directly, you can update the GumCommon NuGet:

* GumCommon - <https://www.nuget.org/packages/FlatRedBall.GumCommon>

If using the Apos.Shapes library, update the library for your target platform:

* Gum.Shapes.MonoGame - <https://www.nuget.org/packages/Gum.Shapes.MonoGame>
* Gum.Shapes.KNI - <https://www.nuget.org/packages/Gum.Shapes.KNI>

For other platforms you need to build Gum from source

See below for breaking changes and updates.

### MonoGameGum.Forms Compatibility Shims Removed

The `MonoGameGum.Forms` compatibility shims that were introduced in [2025 August](https://docs.flatredball.com/gum/gum-tool/upgrading/pages/KwKIOCrw1HgYr8i7tF7E#removal-of-monogamegum.forms-namespace) have been deleted. These shims were marked `[Obsolete(error: true)]` since [2025 October](https://docs.flatredball.com/gum/gum-tool/upgrading/pages/4MlQQipjGVWF3w459FqV#monogamegum.forms-namespace-error), meaning any project referencing them was already a compile error.

If you migrated to `Gum.Forms` namespaces when the error was introduced, no action is needed. If your project still has `using MonoGameGum.Forms.Controls` or similar references, you must update them to the `Gum.Forms` equivalents:

| Old Namespace                         | New Namespace                 |
| ------------------------------------- | ----------------------------- |
| MonoGameGum.Forms                     | Gum.Forms                     |
| MonoGameGum.Forms.Controls            | Gum.Forms.Controls            |
| MonoGameGum.Forms.Controls.Primitives | Gum.Forms.Controls.Primitives |
| MonoGameGum.Forms.Data                | Gum.Forms.Data                |
| MonoGameGum.Forms.DefaultVisuals      | Gum.Forms.DefaultVisuals      |

### Raylib GumService.Initialize Defaults to V3

The parameterless `GumService.Initialize()` overload used by raylib projects previously defaulted to `DefaultVisualsVersion.V2`. It now defaults to `DefaultVisualsVersion.Newest` (V3), matching MonoGame's behavior.

If you need to keep V2 visuals, pass the version explicitly:

```csharp
GumUI.Initialize(DefaultVisualsVersion.V2);
```

### RaylibGum.Input Namespace Removed

Input types have been unified across non-XNA runtimes (raylib, sokol) under a single `Gum.Input` namespace. The `RaylibGum.Input` namespace has been deleted.

The following types moved from `RaylibGum.Input` to `Gum.Input`: `Cursor`, `Keyboard`, `GamePad`, `GamepadButton`, `AnalogStick`, `DPadDirection`, `MouseState`, `ButtonState`, `TouchCollection`, and `TouchLocation`.

Update any `using` directives or fully-qualified references:

| Old                       | New                 |
| ------------------------- | ------------------- |
| `using RaylibGum.Input;`  | `using Gum.Input;`  |
| `RaylibGum.Input.Cursor`  | `Gum.Input.Cursor`  |
| `RaylibGum.Input.GamePad` | `Gum.Input.GamePad` |

MonoGame projects are unaffected — the `MonoGameGum.Input` namespace has not changed. This change only impacts raylib-based projects.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flatredball.com/gum/gum-tool/upgrading/migrating-to-2026-april.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.