Promoting release tracks from beta to pre-release

Dockerfile

@@ -7,6 +7,14 @@ COPY . .
 
 ARG TARGETOS
 ARG TARGETARCH
+ARG VERSION=dev
+ARG BUILDTIME=unknown
+ARG REVISION=unknown
+
+# Make the OCI build metadata available while Angular's static assets are built.
+ENV APP_VERSION=${VERSION} \
+    GIT_COMMIT=${REVISION} \
+    BUILD_DATE=${BUILDTIME}
 
 # Install dependencies
 RUN npm install --cpu ${TARGETARCH} --os ${TARGETOS}
@@ -51,4 +59,4 @@ COPY --from=build /workspace/dist/app/browser /usr/share/nginx/html
 EXPOSE 80 443
 
 # Command to run NGINX in foreground
-CMD ["nginx", "-g", "daemon off;"]
+CMD ["nginx", "-g", "daemon off;"]

angular.json

@@ -73,7 +73,7 @@
                 {
                   "type": "initial",
                   "maximumWarning": "3mb",
-                  "maximumError": "5mb"
+                  "maximumError": "6mb"
                 },
                 {
                   "type": "anyComponentStyle",

docs/local-dev.md

@@ -78,6 +78,23 @@ ng serve
 
 Open your browser and navigate to `http://localhost:4200`
 
+### Build information
+
+`ng serve` uses `src/assets/build-info.json`, which contains development
+fallbacks. The repository's `npm run build` and `npm run build-prod` commands
+generate `dist/app/browser/assets/build-info.json` after Angular finishes.
+Provide release metadata through the same variables used by the Docker build:
+
+```bash
+APP_VERSION=4.20.0-beta.23 \
+GIT_COMMIT=c2c017c146fae040caba559333b35536bfbd1189 \
+BUILD_DATE=2026-08-05T15:13:49.915Z \
+npm run build-prod
+```
+
+If variables are omitted, the generated asset uses the package version and
+reports its commit and build date as `unknown`.
+
 
 ## Note: Recommended setup using Visual Studio Code Workspaces
 
@@ -140,4 +157,4 @@ Example VS Code Workspace configuration:
         ]
     }
 }
-```
+```

docs/usage.md

@@ -2,6 +2,14 @@
 
 The ATT&CK Workbench is a tool intended to allow the ATT&CK community to *explore*, *create*, *annotate* and *share* extensions of ATT&CK. 
 
+## Build Information
+
+The bottom of the primary navigation shows the release versions of the
+Workbench frontend and the connected REST API. Hover over either version to
+see the source commit and build date. If the REST API cannot be reached, its
+version is shown as `unknown` without preventing the rest of the application
+from loading.
+
 ## Exploring ATT&CK
 
 When first instantiated, the ATT&CK Workbench will not include any data. You can use the application to build a custom dataset, or import data from a data provider such as MITRE using the collections browser.
@@ -18,6 +26,14 @@ Objects may exist in multiple collections simultaneously, and objects can exist
 
 You can read more about the technical specifications for a collection, such as the STIX representation of a collection object, in our [collections](/docs/collections.md) document. MITRE's ATT&CK collections and collection index can be found on our [attack-stix-data GitHub repository](https://github.com/mitre-attack/attack-stix-data).
 
+#### Releasing a Release-Track Snapshot
+
+The release preview offers minor and major relative tags as well as an exact `MAJOR.MINOR` version. Relative tags are calculated from the tagged snapshot immediately before the selected draft. When releasing an older draft, the exact version must also remain below the next tagged snapshot; the dialog shows these exclusive bounds. Optional release notes are stored on that snapshot and become the `x-mitre-collection` description in exported STIX bundles.
+
+The release-track page can export the latest snapshot or a selected historical snapshot as a STIX 2.0 bundle, a STIX 2.1 bundle, or Workbench JSON. Historical snapshot exports can also copy a concise summary. Tagged snapshots with a bundle cache use that pinned member graph for deterministic member-only exports in either STIX version.
+
+Each cached snapshot card displays server-generated SHA-256 hashes for the exact UTF-8 JSON files produced by its STIX 2.0 and STIX 2.1 bundle downloads. The adjacent copy buttons copy a hash for external file-integrity verification. Snapshot notes are locked while the bundle is cached; delete the cache, edit the notes, and cache the bundle again to generate matching hashes.
+
 #### Adding a Collection Index
 
 Collection indexes can be added from the collections page. To add a collection index, specify the URL at which the index is found. The application will then provide a preview of the index for you to review before you save. You can also choose from the provided "recommended collection indexes" to quickly connect your Workbench instance to a data provider without having to find the URL yourself. The ATT&CK Workbench is pre-configured to recommend the MITRE ATT&CK collection index in the "add a collection index" interface.
@@ -226,6 +242,8 @@ When creating and/or editing an object, you can add multiple statements and sele
 
 Any object in the knowledge base, except for marking definitions, can be edited, even those imported from collections. Clicking the "edit" button in the toolbar, or the "edit" link in an object list, will bring you to the edit interface for the object. While editing an object, relationships cannot be viewed or created since they are saved independently of the objects they connect.
 
+Domain-bearing ATT&CK objects expose a Domain field that reads and writes the STIX `x_mitre_domains` list. This includes techniques, campaigns, mitigations, groups, software, analytics, assets, data components, data sources, detection strategies, matrices, and tactics. When an existing object is revised, its domains are retained unless the editor explicitly changes them.
+
 #### Editing Matrices
 
 Matrices share the typical fields on objects, including a description supporting markdown, LinkByIds, and citations. Unlike other object types, their IDs serve as identifier for their domain:
@@ -425,6 +443,7 @@ The source and target objects can be changed after the relationship has been cre
 
 Relationships also have a description to provide additional context or to hold citations of relevant reporting. Like all descriptions, those on relationships support citations, LinkByIds, and markdown formatting. Relationships between sub-techniques and techniques however are purely structural and do not support descriptions.
 
+Saving a relationship creates a new relationship revision and returns its connected source and target objects to the *work in progress* workflow state through new SDO revisions. Previously published or snapshot-pinned SDO revisions remain unchanged.
 
 ### Revoking and Deprecating Objects
 
@@ -527,4 +546,4 @@ Within the page showing the list of teams, there is an option to create a new te
 
 ### Editing a team
 
-When viewing a team, click the edit icon in the toolbar to edit it.  You can edit the name, description, or user list of a team at any time.
+When viewing a team, click the edit icon in the toolbar to edit it.  You can edit the name, description, or user list of a team at any time.