Upgrade to 2026.2

Vera 2026.2 adds Record Integrity and Universal Adapter services to the stack and reuses the client secret and public API secret requirements introduced in 2026.1. Follow the steps below to add the new services, configure secrets, then proceed with the database and container upgrades.

Add the Record Integrity services

Vera 2026.2 introduces vera.api.recordintegrity and vera.worker.recordintegrity to power the new Record Integrity queue. The Auto-fix flow also depends on consumers that ship in the 2026.2 images of vera.worker.jira and vera.worker.qtest.

Make sure your logging-settings.json includes entries for both Record Integrity services.

For deployment steps, check out Set up the Record Integrity services.

Add the Universal Adapter services

Vera 2026.2 introduces vera.api.universaladapter and vera.worker.universaladapter to power Universal Adapter integrations.

Before you start the Universal Adapter containers, create the IdentityServer__Secrets__UniversalAdapterModule secret file and set VERA_UNIVERSAL_ADAPTER_HTTP_PORT in your .env file.

Make sure your logging-settings.json includes entries for vera.api.universaladapter and vera.worker.universaladapter. To trace outbound HTTP to connected source systems, also add a Messages UniversalAdapter section.

Download the Vera 2026.2 docker-compose.yml, which includes the Universal Adapter service definitions, or add the services from that file to your existing compose file.

Configure Docker secrets

The Vera 2026.2 docker-compose.yml references secret files that you must create in the Vera Server installation directory. If you upgraded to Vera 2026.1, you should already have the client secrets and public API secrets listed below.

To configure secrets, follow these steps:

1. Add the following files to your data directory (or a subdirectory):

   Client secrets (required since Vera 2026.1)

   • vera_internal_secret.txt

   • IdentityServer__Secrets__JiraAddOn

   • IdentityServer__Secrets__VeraInternal

   • IdentityServer__Secrets__VeraJiraCloudAddOn

   • IdentityServer__Secrets__VeraSamlClient

   • IdentityServer__Secrets__VeraWebPortal

   • IdentityServer__Secrets__VeraUserInfo

   Public API secrets (required since Vera 2026.1)

   • VERA_API_KEY_PEPPER

   • IdentityServer__Secrets__PublicApi

   • PublicApi__InternalAuth__ClientSecret

   Record Integrity secrets (new in Vera 2026.2)

   • IdentityServer__Secrets__RecordIntegrityModule

   Universal Adapter secrets (new in Vera 2026.2)

   • IdentityServer__Secrets__UniversalAdapterModule

   Set the contents of each file to the secret string. For client secrets, make sure the web portal and Jira apps are configured with the same values. The VERA_API_KEY_PEPPER value must match between Vera Server and vera.api.public.

   If you are upgrading from a release prior to 2026.1 and do not yet run the public API service, check out Set up the public API service.

2. Update the Docker Compose file. The Vera 2026.2 docker-compose.yml already includes the required secrets references for each service. If you are merging changes into an existing file instead of replacing it, add the appropriate secrets entries to each Vera container that requires them.

3. At the end of the docker-compose.yml file, add or update the secrets element:

   Copy

   secrets:
       vera_internal_secret:
         file: vera_internal_secret.txt
       VERA_API_KEY_PEPPER:
         file: VERA_API_KEY_PEPPER
       IdentityServer__Secrets__PublicApi:
         file: IdentityServer__Secrets__PublicApi
       PublicApi__InternalAuth__ClientSecret:
         file: PublicApi__InternalAuth__ClientSecret
       IdentityServer__Secrets__RecordIntegrityModule:
         file: IdentityServer__Secrets__RecordIntegrityModule
       IdentityServer__Secrets__UniversalAdapterModule:
         file: IdentityServer__Secrets__UniversalAdapterModule
       IdentityServer__Secrets__JiraAddOn:
         file: IdentityServer__Secrets__JiraAddOn
       IdentityServer__Secrets__VeraInternal:
         file: IdentityServer__Secrets__VeraInternal
       IdentityServer__Secrets__VeraJiraCloudAddOn:
         file: IdentityServer__Secrets__VeraJiraCloudAddOn
       IdentityServer__Secrets__VeraSamlClient:
         file: IdentityServer__Secrets__VeraSamlClient
       IdentityServer__Secrets__VeraWebPortal:
         file: IdentityServer__Secrets__VeraWebPortal
       IdentityServer__Secrets__VeraUserInfo:
         file: IdentityServer__Secrets__VeraUserInfo

4. Update your .env file with any new port variables from the Vera 2026.2 .env file, including:

   Variable	Description
   VERA_RECORD_INTEGRITY_HTTP_PORT	HTTP port for vera.api.recordintegrity
   VERA_UNIVERSAL_ADAPTER_HTTP_PORT	HTTP port for vera.api.universaladapter

Complete the upgrade

After you've configured secrets, proceed with the database and container upgrades:

• Databases – database requirements and MongoDB compatibility.

• Containers – container configurations and microservices.

Enable the GraphQL Console

Vera 2026.2 adds a GraphQL Console and query-engine services for reporting and data export. After you complete the database and container upgrades, deploy the new services and enable the feature flag. For the deployment steps and the Requirements Traceability Matrix template update, check out Enable the GraphQL Console.