Release Notes 1.4.0.3
Metadata
This release documentation version 1.0.
| Release | 1.4.0.3 |
|---|---|
| Release date | 2025-12-19 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.4.0.3+v1.4.0.3-cdeae8e |
| Log Server version | 1.4.0.3+v1.4.0.3-b9b48b4 |
| HostScreen Server version | 1.4.0.3+v1.4.0.3-b9939822 |
| Web Terminal Hub version | 1.4.0.3+v1.4.0.3-bf26350 |
| Web Terminal Client version | 1.4.0.3+v1.4.0.3-026947b6 |
| Management Console | 1.4.0.3+v1.4.0.3-cbc2e18 |
| Log Viewer | 1.4.0.3+v1.4.0.3-f7e3b76 |
.NET Platform
| .NET Release | 8.0.22 |
|---|---|
| .NET Runtime | 8.0.22 |
| ASP.NET Core Runtime | 8.0.22 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| 139.7323afb32591d7d2fb62.js | 352.fd5c67ebb0ef9fdda0f8.js |
| 175.0a68285ebbe0083fee1d.js | 612.a5263c6aa55c9220f544.js |
| 193.ce0b550fd58fcfe9b8c7.js | 637.9018b0b2e4ed3cb78e63.js |
| 195.6fafb87c173c297a4394.js | loader.d95c5a09841350654ce9.js |
| 312.8dd9fa5740d8ec436777.js | main.24b54de1450fa85940ce.js |
| 348.e1aed6380a8e62a5dda6.js |
Upgrade Recommendations
This release is not required to fix any known security issues.
This update is recommended for organisations who use the 5250 protocol and require to pass device name/id to the host or use single character auto-enter fields.
Security Notes
This release does is not required to fix any known security issues.
.NET Security
.NET 8.0.21 is used this release of Jubilant that includes security updates. Maximum severity: High. However, these vulnerabilities are not surfaced in Jubilant. Please see these notable changes.
Node and Nuget Packages Security
There is a known, high severity, security issue in one of the dependencies of the Jubilant client: glob CLI: Command injection via -c/--cmd executes matches with shell:true - https://github.com/advisories/GHSA-5j98-mcp5-4vw2 This vulnerability is not surfaced in the Jubilant client and will be resolved in a future version.
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.
New
None.
Fixed
| ID | Protocols | Description |
|---|---|---|
| HSS.117 | 5250 | Setting a device name that is in use causes an incorrect response |
| WTC.481 | ALL | When a display name is not set display the definition name on the connection tiles |
| WTC.485 | 5250 | The Program Messages screen in 5250 can display a FieldControlWords undefined error |
| WTC.486 | ALL | When no screen is returned the keyboard and the cursor should not be active |
| WTC.488 | 5250 | Single character 5250 auto-enter fields can cause a client error |
Known Issues
| ID | Protocols | Description |
|---|---|---|
| WTC.429 | ALL | On-screen keyboard on small screen devices |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 8.0.22 | All | See .Net Security Notes. |
Change Notes
HSS.117 Setting a device name that is in use causes an incorrect response
When using the device name feature introduced in 1.4.0.2, if a device name was set that was already in use or not yet released by the host then an incorrect response would be sent by Jubilant to the host. This has been resolved in this release.
Please note: Jubilant now responds to a device name being in use by showing a client message and disconnecting the session. If you see this message, please set a new device name via the settings icon on the tile or, if you have just disconnected and wish to re-use the same device name, wait until the host has released it.
WTC.481 When a display name is not set display the definition name on the connection tiles
If a host definition did not have a display name set then the connection tile would not show any text. As of this release the definition name is displayed in the case that no display name is set.
WTC.485 The Program Messages screen in 5250 can display a FieldControlWords undefined error
If a user interacted with the Program Messages screen in 5250 in any way other than just pressing Enter then the client would display a FieldControlWords undefined error. This issue has been resolved in this release.
WTC.486 When no screen is returned the keyboard and the cursor should not be active
If an issue with connecting to the host resulted in no screen being returned then a blank screen was displayed. The keyboard and cursor where active on this screen and interacting with them could cause an error to be displayed. As of this release the screen now displays 'Awaiting Screen' and the keyboard and cursor are inactive.
WTC.488 Single character 5250 auto-enter fields can cause a client error
Interacting with a single character auto-enter field on a 5250 screen could cause the client to display an error. This issue has been resolved in this release.
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.
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 1.0.x build to a 1.1.x or later build.
If upgrading from Jubilant 1.0.x to 1.1.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 Jubilant 1.0.x to 1.1.x, make sure the after install steps are also completed.
Version Validation
Find out how to validate the installed version.