Subject7 version 10.6.4 - 05/26/2026- May require support for upgrade

v10.6.4 has been released!

For help with Subject7, please reach out to [e-mail] 

New

• Subject7 Recorder now supports Shadow DOM capturing using CSS Selectors
• Added support for Inline CSS Selectors that you can add in your step without using Web Locators
• Chrome driver is upgraded to version 148.0.7778.96 and supports Chrome version 148
• Edge driver is upgraded to version 148.0.3967.54 and supports Edge version 148

Improvements

• Improved Switch_Window command to select 'Main' instead of 0 in Handler Index when closing a tab using Subject7 Recorder
• Improved copying REST Connections that use OAuth authentication, where some fields previously lose their values after pasting

Fixes

• Fixed an issue where an error would be displayed when renaming folders under Repository

On-Premise Configurations (PLEASE CHECK NOTES SECTION BELOW THE TABLE)

 It's important to keep all services up to date.

Default Repo URL: registry.gitlab.com/subject7inc (Accessible with Tokens) or use your proxy URL

Container	Image URL	Version
activemq	$RepoURL/docker-containers/activemq:6.2.5.s7-b550	6.2.5.s7-b550
configserver	$RepoURL/configserver/configserver:1.2.3.422	1.2.3.422
grail	$RepoURL/grail/grail:1.1.3.394	1.1.3.394
hera	$RepoURL/hera/hera-service:3.3.2.1104	3.3.2.1104
hydra (optional)	$RepoURL/subject7inc/hydra/hydra:1.1.2.372	1.1.2.372
ml-worker	$RepoURL/ml-worker/ml-worker:2.1.2.351	2.1.2.351
nginx	$RepoURL/docker-containers/nginx:1.24.0.ubi9.s7-b550	1.24.0.ubi9.s7-b550
package-manager/script	$RepoURL/package-manager/package-manager:1.2.77.1	1.2.77.1
postgres	$RepoURL/docker-containers/postgres:15.17.s7-b550	15.17.s7-b550
postgres-backup	$RepoURL/docker-containers/postgres-backup:postgres-backup:15.17.s7-b550	15.17.s7-b550
proof	$RepoURL/platform/platform:proof:10.6.4.13315	10.6.4.13315
proof-worker	$RepoURL/platform/proof-worker:10.6.4.13315	10.6.4.13315
proof-worker-api	$RepoURL/platform/proof-worker-api:10.6.4.13315	10.6.4.13315
storage-service	$RepoURL/storage-service/storage:2.2.2.879	2.2.2.879
webdrivers	$RepoURL/docker-containers/webdrivers:20260513.s7-b550	20260513.s7-b550
XPoint	$RepoURL/platform/xpoint:10.6.4.13315	10.6.4.13315

XPoint/Player update: Yes

Hot deploy: No

Jenkins plugin update: No

JIRA plugin update: No

Important notes: 
Release 10.6.4 runs a long database update (encrypted test case steps migration). Please set the database update flag again: account.database.update.onstart=true and wait patiently until deployment finishes and server starts. 

<role_id> is rotated on every S7 Platform upgrade;
<secret_id> is rotated each time the command is executed;
You must update both values after every platform upgrade;

• Before upgrading the Subject7 Platform, please adjust your main docker-compose.yml file:

  1. “vault” service:

     • remove “user: 0:0“ attribute;

     • add “restart: always“ attribute;
       it should look as follows:

       services:
         ...
         vault:
           image: ${VAULT_IMAGE}
           container_name: vault
           ports:
             - "8200:8200"
           restart: always
           depends_on:
             - message-broker
           ...

  2. “hera” service:

     • adjust the value of depends_on attribute.
       it should look as follows:

       services:
         ...
         hera:
           container_name: hera
           image: "${HERA_IMAGE}"
           ...
           depends_on:
             configserver:
               condition: service_started
             database:
               condition: service_started
             vault:
               condition: service_healthy
           networks:
             ...

       Important Note: if a “Relational Database Service (RDP)” is used, then please skip “database“ value.
       In this case, it should look as follows:

       services:
         ...
         hera:
           container_name: hera
           image: "${HERA_IMAGE}"
           ...
           depends_on:
             configserver:
               condition: service_started
             vault:
               condition: service_healthy
           networks:
             ...

  3. “ml-worker” service (if you already have this):

     • adjust the value of depends_on attribute.
       it should look as follows:

       services:
         ...
         ml-worker:
           container_name: ml-worker
           image: "${ML_WORKER_IMAGE}"
           ...
           depends_on:
             configserver:
               condition: service_started
             vault:
               condition: service_healthy
           networks:
             ...