Subject7 version 10.5.24 - 03/03/2026- May require support for upgrade

v10.5.24 has been released!

New

• A new Downloads icon has been added next to Notifications to improve access to exported content. Exported items will now be available for two days and can be accessed through the Download or Copy Link options.

• Added support for interacting with <object> elements in Subject7 Recorder and Gutenberg extensions

• Xray mapping under Execution Sets will now display multiple pages for newly added results when the user keeps clicking Fetch More Xray Tests
• Map Selection button on Xray mapping under Execution sets no longer overrides the previously selected mappings
• Chrome driver is upgraded to version 145.0.7632.26 and supports Chrome version 145
• Edge driver is upgraded to version 145.0.3800.58 and supports Edge version 145

Improvements

• Improved Gutenberg extension to generate a relative XPath when the captured text contains hyphens or single quotes.

Fixes

• Fixed an issue in Subject7 Recorder where relative XPaths were not captured for elements requiring drag actions.

On-Premise Configurations

NOTE: 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.0.s7-b497	6.2.0.s7-b497
configserver	$RepoURL/configserver/configserver:1.1.15.375	1.1.15.375
grail	$RepoURL/grail/grail:1.0.18.322	1.0.18.322
hera	$RepoURL/hera/hera-service:3.2.14.999	3.2.14.999
hydra (optional)	$RepoURL/subject7inc/hydra/hydra:1.0.11.302	1.0.11.302
ml-worker	$RepoURL/ml-worker/ml-worker:2.0.18.290	2.0.18.290
nginx	$RepoURL/docker-containers/nginx:1.24.0.ubi9.s7-b499	1.24.0.ubi9.s7-b499
package-manager	$RepoURL/package-manager/package-manager:1.2.71.1	1.2.71.1
package-manager scripts link	$RepoURL/Subject7Inc/package-manager/-/packages/55902551	1.2.71.1
postgres	$RepoURL/docker-containers/postgres:15.17.s7-b515	15.17.s7-b515
postgres-backup	$RepoURL/docker-containers/postgres-backup:postgres-backup:15.15.s7-b490	15.15.s7-b490
proof	$RepoURL/platform/platform:proof:10.5.24.12570	10.5.24.12570
proof-worker	$RepoURL/platform/proof-worker:10.5.24.12570	10.5.24.12570
proof-worker-api	$RepoURL/platform/proof-worker-api:10.5.24.12570	10.5.24.12570
storage-service	$RepoURL/storage-service/storage:2.1.18.821	2.1.18.821
webdrivers	$RepoURL/docker-containers/webdrivers:20260218.s7-b490	20260218.s7-b490
XPoint	$RepoURL/platform/xpoint:10.5.24.12570	10.5.24.12570

XPoint/Player update: Yes

Hot deploy: No

Jenkins plugin update: No

JIRA plugin update: No

Special Instructions for this Release

How to update?

1. If the instance uses AWS RDS or any other custom PostgreSQL server then this step should be skipped. If Subject7 PostgreSQL container (database) is used then first create database backups:

   • Navigate to installation dir: cd /opt/subject7

   • Shutdown all containers: sudo ./subject7 down

   • Run database and database-backup containers: sudo ./subject7 up database database-backup

   • Go into database-backup container: sudo docker exec -it database-backup bash

   • Inside /home/subject7 directory of container (usually navigated to on docker exec) run backups creation script: ./database-backup-run.sh

   • Leave container: exit
      

2. Stop all containers: sudo ./subject7 down

3. If Subject7 PostgreSQL container (database) is used read content of .env file and copy somewhere version of database image:

   • Get content: cat .env

   • Find line such as DATABASE_IMAGE=${DOCKER_REPO}/docker-containers/postgres:12.22.s7-b490

   • Copy 12.22.s7-b490 to somewhere

4. Run upgrade as usual: sudo ./subject7 upgrade (if you used any arguments like offline use them too)
   Attention! Upgrade script can fail with message like below:

   ./subject7: line 395: syntax error near unexpected token `(' ./subject7: line 395: `ubject7 down - shutdown the Subject7 platform (all services)'

   If you see it, then everything is ok, upgrade was successful, it is an expected behaviour due to incompatibility of old subject7 script and the new one you will get this error on migration.

   Script will run the following command to get a list of your services listed in docker-compose.yml: 
   sudo docker compose config --services. 
   If it doesn’t find database section it will assume that you use custom database server. 
   
   After that, the script will add extra flag variable to the end of conf/subject7.properties: IS_DB_UPGRADED.
    If you use custom database it will be set to true (IS_DB_UPGRADED=true), if you use PostgreSQL container provided by Subject7 it will be set to false (IS_DB_UPGRADED=false).
    

5. Check the flag IS_DB_UPGRADED in conf/subject7.properties, be sure that flag has the correct value which fits your system (see point #4 above). If the value is incorrect change it with any editor.

6. If Subject7 PostgreSQL container (database) is used, run migration command: sudo ./subject7 upgrade-to-postgres15.
   Script will do the following actions:

   • rename mapped database data folder data/database to data/database-<year>-<month>-<day>-<hour>-<minute>-<second> as another backup point and create new data/database folder

   • run database and database-backup containers

   • find the latest folder in mapped data/database-backups folder, it will be the folder with the backup you created in the beginning

   • restore databases from backups in the latest folder
      

7. Important! If Subject7 PostgreSQL container (database) is used and you executed the migration command above check the information below:

   • Keep in mind that as described above, the script restores/migrates data into data/database folder. After migration is complete, check your database service description in docker-compose.yml.

   • If in the volumes section of the database service you see that the custom folder is mounted instead of ./data/database: then you need to perform a few extra actions manually::

     • Rename this custom mounted folder to keep it as another backup point
     • Copy data/database to the path of the custom folder (rename if required), so that data/database will replace the initial folder by path

     • Set subject7:subject7 ownership with the chown command for the copied folder with the same access rights the renamed custom folder has with chmod

8. Run platform: sudo ./subject7 up.

Rollback

If you use Subject7 PostgreSQL (database) and something goes wrong with database:

1. Stop all services: sudo ./subject7 down

2. Go to .env file with any editor and replace version of database image to the one you copied before in the step #3 of upgrade guide.

3. Change DB folder:

   • Verify that folder with name like data/database-<year>-<month>-<day>-<hour>-<minute>-<second> exists

   • Delete new folder data/database

   • Rename data/database-<year>-<month>-<day>-<hour>-<minute>-<second> to data/database.

4. Run platform: sudo ./subject7 up