From 9846287a237310cf0fc390c08531c88137d68b09 Mon Sep 17 00:00:00 2001 From: christosarvanitis Date: Thu, 14 Aug 2025 16:53:58 +0300 Subject: [PATCH 1/3] chore(docs): Updating 2.36.2 release documentation --- .../armoryspinnaker_v2-36-2.md | 484 ++++++++++++++++++ 1 file changed, 484 insertions(+) create mode 100644 content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md diff --git a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md new file mode 100644 index 0000000000..f88b8569da --- /dev/null +++ b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md @@ -0,0 +1,484 @@ +--- +title: v2.36.2 Armory Continuous Deployment Release (Spinnaker™ v1.36.1) +toc_hide: true +version: 2.36.2 +date: 2025-08-14 +description: > + Release notes for Armory Continuous Deployment v2.36.1. +--- + + + +## 2025-08-14 release notes + +>Note: If you experience production issues after upgrading Armory Continuous Deployment, roll back to a previous working version and report issues to [http://go.armory.io/support](http://go.armory.io/support). + +## Required Armory Operator version + +To install, upgrade, or configure Armory CD 2.36.2, use Armory Operator 1.8.6 or later. + +## Security + +Armory scans the codebase as we develop and release software. Contact your Armory account representative for information about CVE scans for this release. + +## Breaking changes + + +The following configuration properties have been restructured: + +Previous Configuration: + +```yaml +tasks: + days-of-execution-history: + number-of-old-pipeline-executions-to-include: +``` + +New configuration format + +```yaml +tasks: + controller: + days-of-execution-history: + number-of-old-pipeline-executions-to-include: + optimize-execution-retrieval: + max-execution-retrieval-threads: + max-number-of-pipeline-executions-to-process: + execution-retrieval-timeout-seconds: +``` + +These changes improve query performance and execution retrieval efficiency, particularly for large-scale pipeline applications. + +[Performance Improvements for SQL Backend](#performance-improvements-for-sql-backend) + +## Known issues + + +## Highlighted updates + +### Armory Continuous Deployment 2.36.2 Docker images now based on Ubuntu +The Armory Continuous Deployment 2.36.2 Docker images have been updated to use Ubuntu as the base image, replacing the previous Alpine base. +This change enhances compatibility with various libraries and tools, improving overall stability and performance. +Additionally, the new images now include all the necessary dependencies for authentication on a Kebreros server. + +### Pipeline Reference feature is now able to Lazy load the pipeline reference pipelines +In Spinnaker OSS release 1.35.0 Orca introduced a feature flag to reduce the execution size in nested pipelines by +converting PipelineTrigger to PipelineRefTrigger: +{{< highlight yaml "linenos=table,hl_lines=12-13" >}} +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + orca: + executionRepository: + sql: + enabled: true + pipelineRef: + enabled: true +{{< /highlight >}} + +When enabled, child pipeline execution ids are stored in sql instead of the entire child pipeline execution context. + +In Armory CD 2.36.2 this functionality is now extended to make the in-memory representation of the pipelines aware of the pipeline reference +and to not load in-memory a full representation of the pipeline context. To enable this feature in Deck add the following in `settings-local.js`: + +{{< highlight yaml "linenos=table,hl_lines=11" >}} +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + deck: + settings-local.js: | + ... + window.spinnakerSettings.feature.pipelineRefEnabled = true; + ... +{{< /highlight >}} + +*Orca [PR 4842](https://github.com/spinnaker/orca/pull/4842)* +*Deck [PR 10164](https://github.com/spinnaker/deck/pull/10164)* + +### New pipeline stage configuration `backOffPeriodMs` +A new configuration option `backOffPeriodMs` has been added to the pipeline stage configuration. This option allows users +to specify a back-off period in milliseconds for stages that may need to retry operations after a failure. Before this, +pipeline authors had no control over the backoff period. It came from either spinnaker configuration properties or +implementations of RetryableTask.getDynamicBackoffPeriod. + +Additionally, the following configuration options have been added that allow admins to specify globablly the backoff period: +{{< highlight yaml "linenos=table,hl_lines=9-11" >}} +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + orca: + tasks.global.backOffPeriod: + tasks..backOffPeriod: + tasks...backOffPeriod: +{{< /highlight >}} + +*Orca [PR 4841](https://github.com/spinnaker/orca/pull/4841)* + +### Java upgrades + +Java 17 is now the default source and target. Java 11 support has been removed entirely. Please note you may need to add the following JAVA_OPTS options: `--add-exports=java.base/sun.security.x509=ALL-UNNAMED --add-exports=java.base/sun.security.pkcs=ALL-UNNAMED --add-exports=java.base/sun.security.rsa=ALL-UNNAMED` to clouddriver if using GCP accounts due to credentials parsing of certificates. These can set in the [service-settings config](https://spinnaker.io/docs/reference/halyard/custom/#custom-service-settings) . These configs are likely to be added to the defaults in all future releases + +{{< highlight yaml "linenos=table,hl_lines=10" >}} +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + service-settings: + clouddriver: + env: + JAVA_OPTS: "--add-exports=java.base/sun.security.x509=ALL-UNNAMED --add-exports=java.base/sun.security.pkcs=ALL-UNNAMED --add-exports=java.base/sun.security.rsa=ALL-UNNAMED" +{{< /highlight >}} + +### Performance Improvements for Pipeline Executions + +This release includes several optimizations to improve pipeline execution times, particularly for complex pipeline structures. + +Key Improvements + +1. Memorize the `anyUpstreamStagesFailed` extension function to improve time complexity from exponential to linear +2. Optimize `getAncestorsImpl` to reduce time complexity by a factor of N, where N is the number of stages in a pipeline +3. Optimize `StartStageHandler` to only call withAuth (which calls getAncestorsImpl) when + +These enhancements significantly reduce pipeline execution time, with the most notable gains observed in dense pipeline graphs. For example, in the `ComplexPipeline.kt` test scenario, execution time improved from not completing at all to approximately `160ms`. + +*[PR 4824](https://github.com/spinnaker/orca/pull/4824)* + +### Performance Improvements for SQL Backend + +This release enhances the performance of SQL-backed pipeline queries by optimizing database operations, particularly for the API call: + +``` +/applications/{application}/pipelines?expand=false&limit=2 +``` + +which is frequently initiated by Deck and forwarded through Gate to Orca. + +Key Improvements + +- Improved Query Efficiency: Optimized the retrieval of pipeline execution data, significantly reducing database query times. +- Refactored `TaskController`: Externalized configuration properties to allow better flexibility and tuning. +- Enhanced `getPipelinesForApplication()` + - Limits the number of pipeline config IDs queried. + - Processes multiple pipeline config IDs simultaneously. + - Introduces multi-threading to handle batches efficiently. + +*[PR 4804](https://github.com/spinnaker/orca/pull/4804)* + +### Feature: Read Connection Pool for SQL Execution Repository + +This release introduces support for a dedicated read connection pool for specific read-only database queries in `SqlExecutionRepository` + +Key Improvements + +1. New "read" Connection Pool: Allows read operations to be routed to a separate connection pool. +2. Configurable Read Pool: Users can define an additional read connection pool in the SQL configuration. +3. Ensures Data Consistency: Some read queries still rely on recently written data and are not yet converted to use a read replica due to potential replication lag. + +Configuration Example + +To enable the read connection pool, add the following configuration: +```yaml +sql: + connectionPools: + default: + <...> + read: + jdbcUrl: jdbc:... + user: orca_service + password: + connectionTimeoutMs: + validationTimeoutMs: + maxPoolSize: + minIdle: + maxLifetimeMs: + idleTimeoutMs: +``` + +*[PR 4803](https://github.com/spinnaker/orca/pull/4803)* + +### Enhanced pipeline batch update feature + +#### Gate + +Adds a new enpdoint, `POST /pipelines/bulksave`, which can take a list of pipeline configurations to save. The endpoint will return a response that indicates how many of the saves were successful, how many failed, and what the failures are. The structure is + +``` +[ + "successful_pipelines_count" : , + "successful_pipelines" : >, + "failed_pipelines_count" : , + "failed_pipelines" : >> +] +``` + +There are a few config knobs which control some bulk save functionality. The gate endpoint invokes an orca asynchronous process to manage saving the pipelines and polls until the orca operations are complete. + +```yaml +controller: + pipeline: + bulksave: + # the max number of times gate will poll orca to check for task status + max-polls-for-task-completion: + # the interval at which gate will poll orca. + taskCompletionCheckIntervalMs: +``` + +#### Orca + +Updates Orca’s SavePipelineTask to support bulk saves using the updated functionality in the front50 bulk save endpoint. + +With [Orca PR 4781](https://github.com/spinnaker/orca/pull/4781), keys from the stage context’s outputs section can now be removed (there by reducing the context size significantly). At present the following tasks support this feature: + +* PromoteManifestKatoOutputsTask +* WaitOnJobCompletionTask +* ResolveDeploySourceManifestTask +* BindProducedArtifactsTask + + +The [Orca PR 4788](https://github.com/spinnaker/orca/pull/4788) introduced a new CheckIfApplicationExists task that is added to various pipeline stages to check if the application defined in the pipeline stage context is known to front50 and/or clouddriver. The following config knobs are provided so that all of these stages can be individually configured to not perform this check if needed. Default value is set to false for all of them. + +{{< highlight yaml "linenos=table,hl_lines=9-28" >}} +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + orca: + tasks: + clouddriver: + promoteManifestKatoOutputsTask: + excludeKeysFromOutputs: + - outputs.createdArtifacts + - outputs.manifests + - outputs.boundArtifacts + waitOnJobCompletionTask: + excludeKeysFromOutputs: + - jobStatus + - completionDetails + resolveDeploySourceManifestTask: + excludeKeysFromOutputs: + - manifests + - requiredArtifacts + - optionalArtifacts + core: + bindProducedArtifactsTask: + excludeKeysFromOutputs: + - artifacts +{{< /highlight >}} + +Separate config knobs are also provided at the AbstractCheckIfApplicationExistsTask level to determine if clouddriver needs to be queried for the application or not. It is by default set to true, so it is an opt-out capability. the config property is: + +```yaml +tasks: + clouddriver: + checkIfApplicationExistsTask: + checkClouddriver: false # default is true +``` + +This feature runs in audit mode by default which means if checkIfApplicationExistsTask finds no application, a warning message is logged. But when audit mode is disabled through the following property, pipelines fail if application is not found: + +```yaml +tasks: + clouddriver: + checkIfApplicationExistsTask: + auditModeEnabled: false # default is true +``` + +#### Front50 + +Batch update operation in front50 is now atomic. Deserialization issues are addressed. +Configurable controls are added to decide whether cache should be refreshed while checking for duplicate pipelines: + +{{< highlight yaml "linenos=table,hl_lines=9-12" >}} +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + front50: + controller: + pipeline: + save: + refreshCacheOnDuplicatesCheck: false // default is true +{{< /highlight >}} + +Batch update call now responds with a status of succeeded and failed pipelines info. The response will be a map containing information in the following format: + +``` +[ + "successful_pipelines_count" : , + "successful_pipelines" : >, + "failed_pipelines_count" : , + "failed_pipelines" : >> +] +``` + +Here the value for `successful_pipelines` is the list of successful pipeline names whereas the value for `failed_pipelines` is the list of failed pipelines expressed as maps. + + + + + + +### Spinnaker community contributions + +There have also been numerous enhancements, fixes, and features across all of Spinnaker's other services. See the +[Spinnaker v1.36.1](https://www.spinnaker.io/changelogs/1.36.1-changelog/) changelog for details. + +## Detailed updates + +### Bill Of Materials (BOM) + +
Expand to see the BOM +
+
+version: 2.36.2
+timestamp: 2025-08-14 07:29:50
+services:
+  echo:
+    version: 2.36.2
+    commit: 93303566f7d718f115520dd0b00852cfa183f413
+  igor:
+    version: 2.36.2
+    commit: 7fccfb59279c325d5368a82ed9859f9cc7253302
+  kayenta:
+    version: 2.36.2
+    commit: 4b9fb28ad8fa0e4b44fa162691b5d51691d90891
+  orca:
+    version: 2.36.2
+    commit: 7a3859e21f389b81aba72e294243bb41a7653d8f
+  rosco:
+    version: 2.36.2
+    commit: 8e35f1c3560b3b8f7de6fc4a35718b4aee98a47c
+  dinghy:
+    version: 2.36.2
+    commit: 50041173d1a043493409059e7fa5d7a1a80fb553
+  clouddriver:
+    version: 2.36.2
+    commit: feb14e1f16e7d26ed9390c6911da9a9d50038c68
+  front50:
+    version: 2.36.2
+    commit: 08c2d640ec2818a990602c40f22952782af0781f
+  gate:
+    version: 2.36.2
+    commit: 4008ca9592054ea4cb100231dffe13dd8f819367
+  fiat:
+    version: 2.36.2
+    commit: e7412ae8d6a0c4fe765098315696fe24eeb3e2f5
+  terraformer:
+    version: 2.36.2
+    commit: 9756bee07eaabbb25b54812996314c22554ec1c0
+  deck:
+    version: 2.36.2
+    commit: 7a9eab2a2a9c29455d2be8b7655e1495937ba1a4
+  monitoring-daemon:
+    version: 2.26.0
+  monitoring-third-party:
+    version: 2.26.0
+dependencies:
+  redis:
+    version: 2:2.8.4-2
+artifactSources:
+  dockerRegistry: docker.io/armory
+
+
+
+ +### Armory + + +#### Armory Igor - 2.36.1...2.36.2 + + +#### Terraformer™ - 2.36.1...2.36.2 + + +#### Armory Rosco - 2.36.1...2.36.2 + + +#### Armory Gate - 2.36.1...2.36.2 + + +#### Armory Echo - 2.36.1...2.36.2 + + +#### Armory Deck - 2.36.1...2.36.2 + + +#### Armory Orca - 2.36.1...2.36.2 + + +#### Armory Kayenta - 2.36.1...2.36.2 + + +#### Dinghy™ - 2.36.1...2.36.2 + + +#### Armory Front50 - 2.36.1...2.36.2 + + +#### Armory Clouddriver - 2.36.1...2.36.2 + + +#### Armory Fiat - 2.36.1...2.36.2 + + + +### Spinnaker + + +#### Spinnaker Igor - 1.36.1 + + +#### Spinnaker Rosco - 1.36.1 + + +#### Spinnaker Gate - 1.36.1 + + +#### Spinnaker Echo - 1.36.1 + + +#### Spinnaker Deck - 1.36.1 + + +#### Spinnaker Orca - 1.36.1 + + +#### Spinnaker Kayenta - 1.36.1 + + +#### Spinnaker Front50 - 1.36.1 + + +#### Spinnaker Clouddriver - 1.36.1 + + +#### Spinnaker Fiat - 1.36.1 + + From 0fa19f041a5c3c4d26f3f3a72f269447f9d76c63 Mon Sep 17 00:00:00 2001 From: christosarvanitis Date: Thu, 14 Aug 2025 17:00:18 +0300 Subject: [PATCH 2/3] chore(docs): Updating main page --- config.toml | 27 +++++++------------ .../armoryspinnaker_v2-36-1.md | 18 +++++++++++++ .../armoryspinnaker_v2-36-2.md | 18 +++++++++++++ 3 files changed, 45 insertions(+), 18 deletions(-) diff --git a/config.toml b/config.toml index 6fed8851f2..e156d5b49d 100644 --- a/config.toml +++ b/config.toml @@ -139,11 +139,6 @@ languageName ="English" # Weight used for sorting. weight = 1 -[[menu.main]] - name = "CD-as-a-Service" - weight = 2 - url = "https://developer.armory.io/" - [[menu.main]] name = "Armory CD" weight = 3 @@ -179,7 +174,7 @@ weight = 1 [params] # See codenew shortcode deploy-engine-plugin-version = "0.16.8" -armory-version = "2.34.x" +armory-version = "2.36.x" #used in air-gapped matching-oss-version-exact = "1.27.0" # used in agent compat and system requirements @@ -204,7 +199,7 @@ terms_and_conditions = "https://www.armory.io/terms-and-conditions/" # Menu title if your navbar has a versions selector to access old versions of your site. # This menu appears only if you have at least one [params.versions] set. -version_menu = "Armory CD v2.34" +version_menu = "Armory CD v2.36" # Flag used in the "version-banner" partial to decide whether to display a # banner on every page indicating that this is an archived version of the docs. @@ -215,7 +210,7 @@ archived_version = false # Used in the "version-banner" partial to display a version number for the # current doc set. # Also used in the PCM to highlight what version the PCM is for -version = "2.34.x" +version = "2.36.x" # A link to latest version of the Armory CD docs. Used in the "version-banner" partial to # point people to the main Armory CD docs site. @@ -336,17 +331,13 @@ theme = "forest" # at the top of the website. [[params.versions]] - version = "Armory CD v2.31" - githubbranch = "v2.31" - url = "https://v2-31.docs.armory.io/continuous-deployment/" + version = "Armory CD v2.34" + githubbranch = "v2.34" + url = "https://v2-34.docs.armory.io/continuous-deployment/" [[params.versions]] - version = "Armory CD v2.30" - githubbranch = "v2.30" - url = "https://v2-30.docs.armory.io/continuous-deployment/" + version = "Armory CD v2.32" + githubbranch = "v2.32" + url = "https://v2-32.docs.armory.io/continuous-deployment/" -[[params.versions]] - version = "Armory CD v2.28" - githubbranch = "v2.28" - url = "https://v2-28.docs.armory.io/continuous-deployment/" diff --git a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-1.md b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-1.md index 5e19d96792..46c54ab39c 100644 --- a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-1.md +++ b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-1.md @@ -57,6 +57,24 @@ These changes improve query performance and execution retrieval efficiency, part ## Known issues +### Echo Filter enabled pipelines feature +Spinnaker OSS Version 1.31.0 introduced a feature to filter pipelines from front50 , that was disabled by default. +Version 1.35.0 enabled it by default , which is not recommended and can cause issues with automated triggers. +In Armory CD 2.36.2 we recommend to explicitly disable this feature by setting the following configuration: + +``` +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + echo: + pipelineCache: + filterFront50Pipelines: false +``` + ## Highlighted updates ### Java upgrades diff --git a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md index f88b8569da..666c4c574b 100644 --- a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md +++ b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md @@ -57,6 +57,24 @@ These changes improve query performance and execution retrieval efficiency, part ## Known issues +### Echo Filter enabled pipelines feature +Spinnaker OSS Version 1.31.0 introduced a feature to filter pipelines from front50 , that was disabled by default. +Version 1.35.0 enabled it by default , which is not recommended and can cause issues with automated triggers. +In Armory CD 2.36.2 we recommend to explicitly disable this feature by setting the following configuration: + +``` +apiVersion: spinnaker.armory.io/v1alpha2 +kind: SpinnakerService +metadata: + name: spinnaker +spec: + spinnakerConfig: + profiles: + echo: + pipelineCache: + filterFront50Pipelines: false +``` + ## Highlighted updates ### Armory Continuous Deployment 2.36.2 Docker images now based on Ubuntu From 2044bdeed80ff5271d305816c79200963699e6f3 Mon Sep 17 00:00:00 2001 From: christosarvanitis Date: Tue, 19 Aug 2025 16:26:12 +0300 Subject: [PATCH 3/3] chore(docs): Updating release notes for 2.36.3 --- ..._v2-36-2.md => armoryspinnaker_v2-36-3.md} | 92 +++++++++---------- 1 file changed, 46 insertions(+), 46 deletions(-) rename content/en/continuous-deployment/release-notes/rn-armory-spinnaker/{armoryspinnaker_v2-36-2.md => armoryspinnaker_v2-36-3.md} (93%) diff --git a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-3.md similarity index 93% rename from content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md rename to content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-3.md index 666c4c574b..4747ab16f8 100644 --- a/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-2.md +++ b/content/en/continuous-deployment/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-36-3.md @@ -1,8 +1,8 @@ --- -title: v2.36.2 Armory Continuous Deployment Release (Spinnaker™ v1.36.1) +title: v2.36.3 Armory Continuous Deployment Release (Spinnaker™ v1.36.1) toc_hide: true -version: 2.36.2 -date: 2025-08-14 +version: 2.36.3 +date: 2025-08-18 description: > Release notes for Armory Continuous Deployment v2.36.1. --- @@ -18,7 +18,7 @@ FOR EXAMPLE, "Armory Continuous Deployment Release LTS" or "Armory Continuous De ## Required Armory Operator version -To install, upgrade, or configure Armory CD 2.36.2, use Armory Operator 1.8.6 or later. +To install, upgrade, or configure Armory CD 2.36.3, use Armory Operator 1.8.6 or later. ## Security @@ -375,45 +375,45 @@ There have also been numerous enhancements, fixes, and features across all of Sp
Expand to see the BOM 
 
-version: 2.36.2
-timestamp: 2025-08-14 07:29:50
+version: 2.36.3
+timestamp: 2025-08-18 14:22:07
 services:
-  echo:
-    version: 2.36.2
-    commit: 93303566f7d718f115520dd0b00852cfa183f413
+  fiat:
+    version: 2.36.3
+    commit: e7412ae8d6a0c4fe765098315696fe24eeb3e2f5
+  front50:
+    version: 2.36.3
+    commit: 08c2d640ec2818a990602c40f22952782af0781f
+  gate:
+    version: 2.36.3
+    commit: 4008ca9592054ea4cb100231dffe13dd8f819367
   igor:
-    version: 2.36.2
+    version: 2.36.3
     commit: 7fccfb59279c325d5368a82ed9859f9cc7253302
+  terraformer:
+    version: 2.36.3
+    commit: 8453d42107fda5f0c315c8459f523e9182805832
+  rosco:
+    version: 2.36.3
+    commit: 8e35f1c3560b3b8f7de6fc4a35718b4aee98a47c
+  dinghy:
+    version: 2.36.3
+    commit: d36fdf5b496b18212275686d4c9069d72c9dbeb1
+  echo:
+    version: 2.36.3
+    commit: 93303566f7d718f115520dd0b00852cfa183f413
   kayenta:
-    version: 2.36.2
+    version: 2.36.3
     commit: 4b9fb28ad8fa0e4b44fa162691b5d51691d90891
+  deck:
+    version: 2.36.3
+    commit: 0ca57d9581c7d4ce101422b75665b2e22635711a
   orca:
-    version: 2.36.2
+    version: 2.36.3
     commit: 7a3859e21f389b81aba72e294243bb41a7653d8f
-  rosco:
-    version: 2.36.2
-    commit: 8e35f1c3560b3b8f7de6fc4a35718b4aee98a47c
-  dinghy:
-    version: 2.36.2
-    commit: 50041173d1a043493409059e7fa5d7a1a80fb553
   clouddriver:
-    version: 2.36.2
+    version: 2.36.3
     commit: feb14e1f16e7d26ed9390c6911da9a9d50038c68
-  front50:
-    version: 2.36.2
-    commit: 08c2d640ec2818a990602c40f22952782af0781f
-  gate:
-    version: 2.36.2
-    commit: 4008ca9592054ea4cb100231dffe13dd8f819367
-  fiat:
-    version: 2.36.2
-    commit: e7412ae8d6a0c4fe765098315696fe24eeb3e2f5
-  terraformer:
-    version: 2.36.2
-    commit: 9756bee07eaabbb25b54812996314c22554ec1c0
-  deck:
-    version: 2.36.2
-    commit: 7a9eab2a2a9c29455d2be8b7655e1495937ba1a4
   monitoring-daemon:
     version: 2.26.0
   monitoring-third-party:
@@ -430,40 +430,40 @@ artifactSources:
 ### Armory
 
 
-#### Armory Igor - 2.36.1...2.36.2
+#### Armory Igor - 2.36.1...2.36.3
 
 
-#### Terraformer™ - 2.36.1...2.36.2
+#### Terraformer™ - 2.36.1...2.36.3
 
 
-#### Armory Rosco - 2.36.1...2.36.2
+#### Armory Rosco - 2.36.1...2.36.3
 
 
-#### Armory Gate - 2.36.1...2.36.2
+#### Armory Gate - 2.36.1...2.36.3
 
 
-#### Armory Echo - 2.36.1...2.36.2
+#### Armory Echo - 2.36.1...2.36.3
 
 
-#### Armory Deck - 2.36.1...2.36.2
+#### Armory Deck - 2.36.1...2.36.3
 
 
-#### Armory Orca - 2.36.1...2.36.2
+#### Armory Orca - 2.36.1...2.36.3
 
 
-#### Armory Kayenta - 2.36.1...2.36.2
+#### Armory Kayenta - 2.36.1...2.36.3
 
 
-#### Dinghy™ - 2.36.1...2.36.2
+#### Dinghy™ - 2.36.1...2.36.3
 
 
-#### Armory Front50 - 2.36.1...2.36.2
+#### Armory Front50 - 2.36.1...2.36.3
 
 
-#### Armory Clouddriver - 2.36.1...2.36.2
+#### Armory Clouddriver - 2.36.1...2.36.3
 
 
-#### Armory Fiat - 2.36.1...2.36.2
+#### Armory Fiat - 2.36.1...2.36.3