Release Notes 1.4.0.2
Metadata
This release documentation version 1.0.
| Release | 1.4.0.2 |
|---|---|
| Release date | 2025-12-04 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.4.0.2+v1.4.0.2-cdeae8e |
| Log Server version | 1.4.0.2+v1.4.0.2-b9b48b4 |
| HostScreen Server version | 1.4.0.2+v1.4.0.2-74337167 |
| Web Terminal Hub version | 1.4.0.2+v1.4.0.2-bf26350 |
| Web Terminal Client version | 1.4.0.2+v1.4.0.2-041ce1a4 |
| Management Console | 1.4.0.2+v1.4.0.2-cbc2e18 |
| Log Viewer | 1.4.0.2+v1.4.0.2-f7e3b76 |
.NET Platform
| .NET Release | 8.0.21 |
|---|---|
| .NET Runtime | 8.0.21 |
| ASP.NET Core Runtime | 8.0.21 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| 139.8558c7bbe4c35c14e949.js | 352.fa952e83559d5e15215b.js |
| 175.b3eebb295a7631c9a802.js | 612.34b1303a8324ce622e14.js |
| 193.d77908f67f57952a2956.js | 637.9604552952207d7cbe9b.js |
| 195.73de01ecb8bedf370764.js | loader.d95c5a09841350654ce9.js |
| 312.d39ba14c2a4fc73df722.js | main..4179bdaced65336a42a.js |
| 348.08572cbbb1d757612e2a.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.
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.116 | 5250 | Add the ability to set the device name |
Known Issues
| ID | Protocols | Description |
|---|---|---|
| WTC.429 | ALL | On-screen keyboard on small screen devices |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 8.0.21 | All | See .Net Security Notes. |
Change Notes
HSS.116 Add the ability to set the device name
A new feature has been added to allow the setting of a device name in the 5250 protocol. Device names are passed to the host by setting an LU Name in the client. Using this feature requires a manual change to the host definition. The definition files are located in C:\Program Files\Flynet\Jubilant\HostScreenServer\Definitions by default. Edit the appropriate file in an editor such as Visual Studio Code and set the value of luMode to one of the following values:
- Hidden - users will not be prompted to enter an LU, this is the default
- Optional - users will not be prompted to enter an LU but may do so by clicking on Settings on the host's tile
- Required - users will be prompted for and must enter an LU. The LU can be changed by clicking on Settings on the host's tile
We recommend that you make a backup of your host definition before making any changes.
Once the changes have been made, you can have Jubilant load them by running Restart Jubilant Host Screen Server and IIS from the Start Menu. Note that this will disconnect all user on the server.
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.