Table of Contents

Release Notes 1.6.0.20 LTS

This is the 4th release in the 1.6.0 line of LTS releases, built with .NET 10.0.15.

Metadata

This release documentation version 1.0.

Release 1.6.0.20
Release date 2026-11-18
Release type Full Release
Future LTS (Long Term Support)
Server version 1.6.0.20+1.6.0.20-LTS-3fcaad97
Log Server version 1.6.0.20+1.6.0.20-LTS-1357f753
HostScreen Server version 1.6.0.20+1.6.0.20-LTS-fa0923f8
Web Terminal Hub version 1.6.0.20+1.6.0.20-LTS-d54d648c
Web Terminal Client version 1.6.0.20+1.6.0.20-LTS-c38ccc7e
Management Console 1.6.0.20+1.6.0.20-LTS-b98b83cb
Log Viewer 1.6.0.20+1.6.0.20-LTS-1ea8114f

.NET Platform

.NET Release 10.0.15
.NET Runtime 10.0.15
ASP.NET Core Runtime 10.0.15
Notable changes Link

Web Terminal Client Renderer File Names (checksum)

Location: Program Files\Flynet\Jubilant\WebTerminal\web

139.e22bd41c597211f407aa.js 175.f4d28852ecb3368547ef.js
193.6b44c1e676954117d790.js 195.e4384d32ab71143dc71e.js
264.b39959fd872560504d9c.js 312.1d039ef14b1e132da0e5.js
348.b5805f616563e0c1f744.js 352.ed0f3ceb9173d36f30b9.js
576.7ba84d69e2dcb540e4dd.js 637.0cdc135d972be8a033c4.js
952.179d7978014e8660394b.js loader.25292ba42daca28a138e.js
main.39d5429e659f4250f029.js

Fixed Since v1.6.0.17

ID Protocols Description
SB!53 5250 Preserve 5250 screen data during save and restore
HSS!135 5250 Correct 5250 SysReq handling
WTC!563 Not specified Keep text visible beneath the underline cursor when printing
WTC!566 Not specified Remove gaps from printed option fields
WTC!572 Not specified Apply print colors consistently to bottom borders

Change Notes

SB!53 — Preserve 5250 screen data during save and restore

Saving and restoring a 5250 screen now preserves the entered data. Integration testing confirmed that text entered before saving was still present after restoring the screen.

HSS!135 — Correct 5250 SysReq handling

Corrected the 5250 SysReq message and handling of the host's cancel-invite response. Integration testing verified the updated message and response sequence.

WTC!563 — Keep text visible beneath the underline cursor when printing

Printing now retains a character that is beneath the underline cursor instead of hiding it. A before-and-after print check confirmed the character remains visible.

WTC!566 — Remove gaps from printed option fields

Corrected gaps in option-entry fields when printing. A before-and-after check confirmed the gaps were no longer visible.

WTC!572 — Apply print colors consistently to bottom borders

Bottom borders now use the selected print foreground color, preventing their colors from being overridden during printing.

Installation

Fresh Install

Please see the Jubilant Admin Manual for Fresh Install Instructions.

Upgrade

Note

Please note the specials steps below if upgrading from a version before 1.6.x.

If upgrading from a version of before v1.6.x extra steps must be carried out before and after the install steps below.

Upgrade is carried out using Jubilant scripts.

  1. Unzip the installer into a folder.
  2. Close any web browsers.
  3. Close any Services windows.
  4. Open PowerShell ISE as Administrator.
  5. In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
  6. Run the required script by pressing the green play / run script button on the toolbar.
  7. The upgrade of Jubilant is complete.

If this is an upgrade from before 1.6.x, make sure the after install steps are also completed.

Version Validation

Find out how to validate the installed version.

Security

.NET Security

Vulnerabilities Fixed in this Release

There were no .NET security updates in this build.

General .NET Vulnerabilities Fixed in this Release

This release uses .NET Runtime 10.0.15 and ASP.NET Core Runtime 10.0.15. The previous release used the same runtime versions, so there are no new .NET security fixes in the version range for this release. There is no highest severity category to report, and no new high or critical .NET vulnerabilities were identified for the product endpoints.

Based on the documented .NET and Node.js changes, this release is not recommended solely for security reasons.

Node Security

There were no Node.js security updates in this build.