--- title: "April 2025 quarterly release" description: "What changed in Guardian Classic in the April 2025 quarterly release." product: "Guardian" edition: "Classic" type: "reference" url: "https://docs.cloudhouse.com/guardian/classic/what-s-new/2-previous-release/2025/quarterly/q2/april-2025/" --- # April 2025 quarterly release For help upgrading to the latest version, contact your Cloudhouse Representative. The following table describes each component available to upgrade within this release of Guardian. Applies to: `Guardian Classic` !!! tip For more information on the known issues currently present within Guardian, see [Known Issues](https://docs.cloudhouse.com/guardian/classic/known-issues/known-issues/index.md). | Release Date | Guardian Platform | Guardian Web | Linux Agent | | --- | --- | --- | --- | | 30th April 2025 | V4 | V3.54.0 | V5.42.0 | ## Guardian web application v3.54.0 Here's what's included in V3.54.0 of the Guardian web application as part of the April 2025 quarterly release. ### New features The following new features are included within this release of the Guardian web application. #### Secret Server Integration to retrieve external credentials You can now integrate Guardian with Secret Server to securely retrieve credentials from your organisation’s existing Secret Server account. This allows you to use external credential storage instead of saving credentials directly in Guardian. To enable the integration, specify your Secret Server instance and the folder path(s) where the credentials are stored. The retrieved credentials will then be available when adding Linux, Windows, or Network device nodes. For more information, see [Secret Server Credentials](https://docs.cloudhouse.com/guardian/classic/what-s-new/2-previous-release/2025/quarterly/q2/secret-server-credentials/index.md). ### Other enhancements The following additional enhancements are included within this release of the Guardian web application. #### New dynamic node group for Debian nodes We have now added Debian nodes to the list of node types that, when added to Guardian for the first time, trigger the creation of a dynamic node group within the **Monitored** tab (**Inventory** > **Monitored**). For example, if you add a Debian 11 node to Guardian for the first time, an overarching 'Debian' dynamic node group will be created for all future Debian node types, as well as an additional 'Debian 11' group that will exclusively add any future Debian 11 node types. !!! tip For more information on dynamic node groups, see [Static / Dynamic Node Groups](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md#static-dynamic-node-groups). #### Improvements to integrations tab functionality As part of our continuous efforts to improve usability, we have made a minor improvement the optional **Credentials** tab (**Inventory** > **Credentials**) functionality. Previously, to edit a set of credentials, you had to click the **Ellipsis** button (![Ellipses](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/buttons/ellipses.png)) and then select **Edit**. Now, you can click anywhere on a credential's row to display the **Update Credentials** page. For more information, see [Credentials](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/credentials/index.md). !!! tip To enable the optional **Credentials** tab, contact your Cloudhouse Representative. ![Credentials tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2025/april/credentials-tab.png) #### Improved readiness check tolerance The `core_api` readiness checks have been updated to allow longer response times before marking a failure. The readiness checks now have longer timeouts, giving services more time to respond before they are marked as failed. #### Increased priority for scheduled job creation Scheduled job creation tasks are now given higher priority and no longer wait behind other delayed jobs. This change ensures that scheduled jobs are created on time, even when the queue is busy. ### Fixed issues The following issues have been fixed within this release of the Guardian web application. #### GWB-6174 – Scheduled jobs page crashing If the original skin on the **Job Schedule** tab (**Control** > **Job Schedule**) was enabled, trying to access the page was resulting in a time out error. This issue has now been fixed in V3.54.0 of Guardian, when accessing the **Job Schedule** tab, the page loads as expected regardless of the skin applied. !!! tip For more information on the new **Job Schedule** skin, contact your Cloudhouse Representative. #### GWB-6088 – Duplicate file upload section when editing GCP nodes On the **Edit GCP Node** page, Guardian was incorrectly displaying two **GCE service account JWT token** file upload sections. This issue has now been fixed in V3.54.0 of Guardian, when editing a GCP node, there is only one **GCE service account JWT token** file upload section. ![Edit gcp node](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2025/april/edit-gcp-node.png) ## Linux Agent v5.42.0 Here's what's included in V5.42.0 of the Linux Agent as part of the April 2025 quarterly release. ### New features There are no new features included within this release of the Linux Agent. ### Other enhancements There are no additional enhancements included within this release of the Linux Agent. ### Fixed issues The following issues have been fixed in this release of the Linux Agent. #### GLA-881 – Unable to diff VPC subnet route tables An issue was occurring with the Linux Agent whereby scanning a VPC subnet in AWS was resulting in the scanned configuration items displaying irregularly. Complete the following steps to replicate the issue: 1. In AWS, create a VPC subnet. 2. Attach or create a new route table. 3. Use a new or existing AWS integration with Guardian to detect existing VPC subnets. 4. Once detected, scan the new VPC subnet node in Guardian. 5. In AWS, update the route table attached to the VPC subnet. Make sure to save your changes. 6. In Guardian, re-scan the VPC subnet node. Looking at the node scan results page, the route tables for the VPC node were then displaying as a list of text objects, without the ability to generate a difference report for each configuration item between one scan and the next. ![Linux agent 1](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2025/april/linux-agent-1.png) However, this issue has now been fixed in V5.42.0 of the Linux Agent. Completing the above steps results in each route being displayed separately and with the ability to difference any configuration changes between scans (as expected). ![Linux agent 2](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2025/april/linux-agent-2.png)