v1.3.0-mc26.2-release

• Added support for Minecraft 26.2 with refreshed release dependencies.
• Fixed update checks selecting the wrong release metadata when multiple entries target the same Minecraft version.
• Fixed server-defined toast notices so current-version entries can show a toast without update download metadata.
• Kept fullscreen and chat update prompts limited to entries with a newer version.
• No local config changes are required.

v1.3.0-mc26.1.x-release

• Fixed server-defined toast notices so Minecraft 26.1.x entries can show a toast even when the installed pack version is current.
• Kept fullscreen and chat update prompts limited to entries with a newer version.
• Allowed toast-only current-version notices without requiring update download metadata.
• Rebuilt release artifacts for Minecraft 26.1.x.
• No local config changes are required.

v1.2.0-mc26.1.x-release

• Fixed update checks selecting the wrong release metadata when multiple entries target the same Minecraft version.
• Added optional loader matching for server update JSON entries.
• Rebuilt release artifacts for Minecraft 26.1.x.
• No local config changes are required.

v1.1.0-mc.26.1.x-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.

v1.1.0-mc.1.21.9-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.

v1.1.0-mc.1.21.8-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.

v1.1.0-mc.1.21.7-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.

v1.1.0-mc.1.21.6-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.

v1.1.0-mc.1.21.5-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.

v1.1.0-mc.1.21.4-release

• Fixed update checks failing when update metadata URLs return HTTP redirects.
• Added redirect handling for GitLab latest release permalink URLs.
• Improved update-check errors for redirect loops, unsupported URL schemes, empty responses, non-successful responses, and invalid JSON.
• Blocked unsafe HTTPS-to-HTTP redirects while keeping existing update metadata unchanged.
• No config changes are required.