Release Notes 1.6.0.12 LTS
This is the second release in the 1.6.0 line of LTS releases, built with .NET 10
Metadata
This release documentation version 1.0.
| Release | 1.6.0.12 |
|---|---|
| Release date | 2026-09-25 |
| Release type | Full release |
| Future | LTS (Long Term Support) |
| Server version | 1.6.0.12+v1.6.0.12-LTS-3fcaad9 |
| Log Server version | 1.6.0.12+v1.6.0.12-LTS-1357f75 |
| HostScreen Server version | 1.6.0.12+v1.6.0.12-LTS-8337ee5 |
| Web Terminal Hub version | 1.6.0.12+v1.6.0.12-LTS-d96979b |
| Web Terminal Client version | 1.6.0.12+v1.6.0.12-LTS-1286857 |
| Management Console | 1.6.0.12+v1.6.0.12-LTS-988eb14 |
| Log Viewer | 1.6.0.12+v1.6.0.12-LTS-a59d6d6 |
.NET Platform
| .NET Release | 10.0.12 |
|---|---|
| .NET Runtime | 10.0.12 |
| ASP.NET Core Runtime | 10.0.12 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| 139.19a9153c8008fbccbb4c.js | 175.00150f5ec4b1c0c5d5d7.js |
| 193.b2d3b9069542c3e95ab2.js | 195.e7287138be0e7bd7f99c.js |
| 264.3f70d2733065bb50ca31.js | 312.a3a9cb31838ab2d7f4ec.js |
| 348.82112b0de69fee4f33d5.js | 352.b71936792f0a485478f5.js |
| 637.5da779567e9e7d68673c.js | 945.5a1b4c367cbbce689476.js |
| 952.fb6ec946ad3f08b25385.js | loader.25292ba42daca28a138e.js |
| main.54c7ee64e60729ddaf28.js |
Upgrade Recommendations
This release is recommended for all users. The upgrade to .NET 10 includes many security and performance updates.
Security Notes
None
.NET Security
.NET 10.0.12 used in this release of Jubilant includes security updates. Maximum severity: High. However, these vulnerabilities are not surfaced in Jubilant. Please see these notable changes.
Node and Nuget Packages Security
None
High Importance Fix Notes
None
In this Release
Preview
The preview version of Automations (macros) first available in 1.3.1.3 continues to be improved. If you are interested in working with the preview, please contact support@flynet.email for more information.
Fixed Since v1.6.0.9
| ID | Protocols | Description |
|---|---|---|
| WTA.115 | ALL | Fix host pipelines do not have access to the ClaimsPrincipal |
| WTA.118 | ALL | Feature add setting of client ping ticks on a SendAction |
| WTA.120 | ALL | Feature rapid detection of browser/tab closure |
| WTC.544 | ALL | Fix default automation error |
| WTC.545 | ALL | Fix pressing TAB with the cursor in the position immediately before an entry field should tab into the field |
| WTC.546 | ALL | Fix null value causing red error screen |
| WTC.548 | ALL | Feature add signalling of session closure with pagehide event |
Known Issues
| ID | Protocols | Description |
|---|---|---|
| WTC.429 | ALL | On-screen keyboard on small screen devices |
| WTC.492 | ALL | Screen size calculations are slightly off |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 10.0.12 | All | See .Net Security Notes. |
Change Notes
WTA115 Fix host pipelines do not have access to the ClaimsPrincipal
Host pipelines erroneously did not have access to the ClaimsPrincipal (and thus a user's claims). This has been resolved in this release.
WTA118 Feature add setting of client ping ticks on a SendAction
The WTA now updates the client ping ticks when it receives a SendAction (AID key) from the client. The impact of this is that, if a client ping timeout is set, the client will not timeout until client ping timeout seconds after the last SendAction.
WTA120 Feature rapid detection of browser/tab closure
A feature has been added to allow the closure of a session hub-side when a user closes the browser/tab in which the session is open. This feature includes a rapid heart-beat for use where the browser does not support other methods of tab closure detection.
This feature is controlled by the following section in the WebTerminalsSettings.json file:
"BrowserClosure": {
"DisconnectHostSessionOnClose": true,
"DisconnectSessionOnlyWithHubDisconnect": true,
"HeartBeatDisconnectBelowSeconds": 7,
"HeartBeatSeconds": 5,
"HeartBeatWhen": "UnsupportedFeatureFallback"
},
DisconnectHostSessionOnClose (default: true) If true, then session will be closed when the user closes the browser/tab. If false, then session will remain until the are timed-out by one of the timeouts. DisconnectSessionOnlyWithHubDisconnect (default: true) If true, then sessions will only be closed when both the client and the hub disconnect notifications have been received. If false, then sessions will be closed as soon as the client notification is received. HeartBeatDisconnectBelowSeconds (default: 7) If a heart-beat is in use, sets the threshold below which sessions will be disconnected. HeartBeatSeconds (default: 5) If a heart-beat is in use, the frequency of the heart-beat. HeartBeatWhen (default: UnsupportedFeatureFallback, other values: Never, Always) Sets the circumstances under which a heart-beat will be used. The default is to use a heart-beat when the browser does not support the Navigator: sendBeacon() method normally used to detect tab closure. Currently the only applies to Safari.
WTC544 Fix default automation error
There was an issue where the client would automatically generate a default automation even though the automations feature was disabled. This has been fixed in this release.
WTC545 Fix pressing TAB with the cursor in the position immediately before an entry field should tab into the field
There was an issue where pressing TAB whilst the cursor was in the position immediately before the start of an entry field did not tab into the field. This has been resolved in this release.
WTC546 Fix null value causing red error screen
There was an error where a null value sent to the client could cause a red error screen to be shown. This has been resolved in this release.
WTC548 Feature add signalling of session closure with pagehide event
The client now uses the pagehide event to signal the closure of the browser/tab.
WTC.429 On-screen keyboard on small screen devices
On small screen devices the on-screen keyboard can be difficult to use. The work around is to define a new keyboard layout and select it via the settings.
WTC.492 Screen size calculations are slightly off
Under certain, rare, circumstances an issue with screen size calculations can cause the top line of the screen to be partly or wholly obscured. This usually occurs when the host changes the screen resolution. The work around is either to turn on stretch to fit in the settings menu or to resize the browser window, changing its width until the top line is visible.
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.
- Unzip the installer into a folder.
- Close any web browsers.
- Close any Services windows.
- Open PowerShell ISE as Administrator.
- In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
- Run the required script by pressing the green play / run script button on the toolbar.
- 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.