Daily release/05 22 25 night

src/content/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx

@@ -5187,6 +5187,51 @@ For a configuration example, see our documentation for the [node agent url obfus
   </Collapser>
 </CollapserGroup>
 
+## GCP Cloud Run [#gcp_cloud_run]
+
+<CollapserGroup>
+  <Collapser
+    id="gcp_cloud_run"
+    title="gcp_cloud_run.use_instance_as_host"
+  >
+    <table>
+      <tbody>
+        <tr>
+          <th>
+            Type
+          </th>
+
+          <td>
+            Boolean
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            Default
+          </th>
+
+          <td>
+            `true`
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            [Environ variable](#environment)
+          </th>
+
+          <td>
+            `NEW_RELIC_GCP_CLOUD_RUN_USE_INSTANCE_AS_HOST`
+          </td>
+        </tr>
+      </tbody>
+    </table>
+
+    If true, the agent will use the Cloud Run ID from the GCP metadata to set the hostname of the running application.
+  </Collapser>
+</CollapserGroup>
+
 ## Worker Threads [#worker-threads]
 
 In agent versions prior to 11.0.0, the agent ran in both main and worker threads.  In version 11.0.0 the agent stopped running in worker threads due to its incompatibility with our async context propagation. The ability to run in worker threads was restored in version 11.3.0 but you must set `worker_threads.enabled` to `true`.  The behavior of running in the worker threads varies and we do not officially support it. Some things like metrics generation, and self contained transaction traces may work but this is a use at your own risk capability.

src/content/docs/data-apis/manage-data/drop-data-using-nerdgraph.mdx

@@ -17,7 +17,7 @@ freshnessValidatedDate: never
 <Callout variant="important">
   As of May 21, 2025, new customers can no longer use NRQL drop rules. Leverage [New Relic Pipeline Control](/docs/new-relic-control/pipeline-control/overview/). Pipeline cloud rules are the direct replacement of NRQL drop rules, and pipeline gateway can also help manage data. 
 
-  [NRQL drop rules will be end of life](/eol/2025/06/drop-rule-filter) January 7, 2026.
+  [NRQL drop rules will be end of life](/eol/2025/05/drop-rule-filter) January 7, 2026.
 </Callout>
 
 One way to [manage your data ingest](/docs/data-apis/manage-data/manage-data-coming-new-relic) is to set up data dropping rules. With data dropping you can:

src/content/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/infra-agent-inventory-reset.mdx

@@ -0,0 +1,48 @@
+---
+title: Force an inventory reset from the infrastructure agent
+type: troubleshooting
+tags:
+  - Infrastructure
+  - Infrastructure monitoring troubleshooting
+  - Troubleshoot infrastructure
+freshnessValidatedDate: 2025-05-21
+---
+
+## Problem [#problem]
+
+The agent is working but some of the metadata or inventory data appears incorrect, and the local caching is preventing correct data to be sent from the infrastructure agent.
+
+## Solution [#solution]
+
+Linux
+Stop the Infrastructure Agent
+```
+systemctl stop newrelic-infra
+```
+Delete temporary files
+```
+rm -rf /var/db/newrelic-infra/data
+```
+Start the Infrastructure Agent
+```
+systemctl start newrelic-infra
+```
+
+Windows
+In an Administrator PowerShell prompt, stop the Infrastructure Agent
+```
+net stop newrelic-infra
+```
+Delete temporary files
+```
+Remove-Item -Path “C:\ProgramData\New Relic\newrelic-infra\data” -Recurse -Force
+```
+Start the Infrastructure Agent
+```
+net start newrelic-infra
+```
+
+## Cause [#cause]
+
+The agent caches metadata & inventory data locally, to determine what delta to send.
+In some situations, it might be desired to reset this local cache / state, so that all data is sent accross. 

src/content/docs/logs/ui-data/drop-data-drop-filter-rules.mdx

@@ -16,7 +16,7 @@ freshnessValidatedDate: never
 <Callout variant="important">
   As of May 21, 2025, new customers can no longer use NRQL drop rules via the logs management UI. Leverage [New Relic Pipeline Control](/docs/new-relic-control/pipeline-control/overview). Pipeline cloud rules are the direct replacement of NRQL drop rules, and pipeline gateway can also help manage data. 
 
-  [NRQL drop rules will be end of life](/eol/2025/06/drop-rule-filter) January 7, 2026.
+  [NRQL drop rules will be end of life](/eol/2025/05/drop-rule-filter) January 7, 2026.
 </Callout>
 
 After log event data has been sent to New Relic, it can either be stored in our NRDB database or dropped (discarded). To drop log data, you can use the logs management UI, as explained in this document. You can also use [NerdGraph to drop data](/docs/accounts/accounts/data-management/drop-data-using-nerdgraph). NerdGraph is our GraphQL Explorer.

src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1640.mdx

@@ -0,0 +1,17 @@
+---
+subject: Infrastructure agent
+releaseDate: '2025-05-22'
+version: 1.64.0
+---
+A new version of the agent has been released. Follow standard procedures to [update the Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent).
+New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is [Infrastructure agent 1.51.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510/).
+
+## Changed
+* Fix: Fixed hash character escaping in nri-flex YAML config parsing [#2028](https://github.com/newrelic/infrastructure-agent/pull/2028)
+* Fix: Removed trailing slash in mandatory prefix when path is empty [#2037](https://github.com/newrelic/infrastructure-agent/pull/2037)
+* Bumped fluent bit version to 3.2.10 [#2045](https://github.com/newrelic/infrastructure-agent/pull/2045)
+* Chore(deps): Updated dependency newrelic/nri-docker to v2.5.0 [#2027](https://github.com/newrelic/infrastructure-agent/pull/2027)
+* Chore(deps): Updated dependency newrelic/nri-prometheus to v2.25.0 [#2016](https://github.com/newrelic/infrastructure-agent/pull/2016)
+* Bumped dependency versions [#2046](https://github.com/newrelic/infrastructure-agent/pull/2046)
+* Chore: Upgraded go version to 1.23.8 [#2059](https://github.com/newrelic/infrastructure-agent/pull/2059)
+* Chore: Updated log level in [#2053](https://github.com/newrelic/infrastructure-agent/pull/2053)

src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-40-0.mdx

@@ -0,0 +1,11 @@
+---
+subject: Kubernetes integration
+releaseDate: '2025-05-21'
+version: 3.40.0
+---
+
+For a detailed description of changes, see the [release notes](https://github.com/newrelic/nri-kubernetes/releases/tag/v3.40.0).
+
+This integration is included in the following chart versions:
+* [newrelic-infrastructure-3.45.0](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.45.0)
+* [nri-bundle-5.0.124](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-5.0.124)

src/content/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.290.1.mdx

@@ -0,0 +1,24 @@
+---
+subject: Browser agent
+releaseDate: "2025-05-21"
+version: 1.290.1
+downloadLink: https://www.npmjs.com/package/@newrelic/browser-agent
+features: []
+bugs: ["Silence setting getter only harvestCount message"]
+security: []
+---
+
+## v1.290.1
+
+### Bug fixes
+
+#### Silence setting getter only harvestCount message
+The warning that results from the agent attempting to overwrite the runtime `harvestCount` will be correctly silenced.
+
+## Support statement
+
+New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach [end-of-life](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Release dates are reflective of the original publish date of the agent version.
+
+New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this [status dashboard](https://newrelic.github.io/newrelic-browser-agent-release/) for more information.
+
+Consistent with our [browser support policy](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), v1.290.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-17, and Firefox 128-138. For mobile devices, v1.290.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.

src/content/docs/release-notes/streaming-release-notes/streaming-mobile-release-notes/streaming-android-agent-25-03-03.mdx

@@ -0,0 +1,31 @@
+---
+subject: Streaming Video & Ads for Mobile
+title: Media agent for Android v3.0.0
+releaseDate: '2025-03-03'
+version: 3.0.0
+metaDescription: Release notes for Media agent for Android version 3.0.0
+---
+
+## New features and enhancements
+
+- **New Event Types Introduced**
+  - **VideoAction**: This event type represents standard actions related to video playback and interaction.
+  - **VideoErrorAction**: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
+  - **VideoAdAction**: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
+  - **VideoCustomAction**: A flexible event type for custom actions and interactions within video applications.
+
+## Deprecations
+- **MobileVideo**
+  - The `MobileVideo` event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.
+
+## New attributes introduced
+- We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, Please [refer to the data model documentation](https://github.com/newrelic/video-agent-android/blob/v3.0.0/DATAMODEL.md) for more details.
+
+## Impact and actions required
+- **Transition from PageAction**: Users currently tracking `PageAction` events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
+- **Update Implementations**: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
+- **Testing & Validation**: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.
+
+## Additional information
+
+For more details on implementing these changes, refer to the updated documentation and integration guides available [here]. Should you have any questions or require further assistance, please reach out to our support team.

src/content/docs/release-notes/streaming-release-notes/streaming-mobile-release-notes/streaming-android-agent-25-03-05.mdx

@@ -0,0 +1,11 @@
+---
+subject: Streaming Video & Ads for Mobile
+title: Media agent for Android v3.0.1
+releaseDate: '2025-03-05'
+version: 3.0.1
+metaDescription: Release notes for Media agent for Android version 3.0.1
+---
+
+### Fix
+
+- Added method to set, `userId` for ads

src/content/docs/release-notes/streaming-release-notes/streaming-mobile-release-notes/streaming-ios-agent-25-03-03.mdx

@@ -0,0 +1,41 @@
+---
+subject: Streaming Video & Ads for Mobile
+title: Media agent for iOS v3.0.0
+releaseDate: '2025-03-03'
+version: 3.0.0
+metaDescription: Release notes for Media agent for IOS version 3.0.0
+---
+
+## New features and enhancements
+
+- **New Event Types Introduced**
+  - **VideoAction**: This event type represents standard actions related to video playback and interaction.
+  - **VideoErrorAction**: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
+  - **VideoAdAction**: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
+  - **VideoCustomAction**: A flexible event type for custom actions and interactions within video applications.
+
+## Deprecations
+
+- **MobileVideo**
+  - The `MobileVideo` event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.
+
+## New attributes introduced
+
+- We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types
+  Please [refer to the data model documentation](https://github.com/newrelic/video-agent-ios/blob/v3.0.0/DATAMODEL.md) for more details.
+Event Types
+• VideoAction: Events triggered by general video interactions, such as starting, pausing, or seeking.
+• VideoAdAction: Events related to ad playback, such as starting, completing, or skipping an ad.
+• VideoErrorAction: Events triggered by errors encountered during video or ad playback.
+• VideoCustomAction: Custom events defined to capture specific actions or interactions beyond default event types.
+
+## Impact and actions required
+
+- **Transition from MobileVideo**: Users currently tracking `MobileVideo` events should adapt their implementations to utilise the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
+- **Update Implementations**: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
+- **Testing & Validation**: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.
+
+## Additional information
+
+For more details on implementing these changes, refer to the updated documentation and integration guides available [here]. Should you have any questions or require further assistance, please reach out to our support team.
+

src/data/whats-new-ids.json

@@ -375,5 +375,6 @@
   "/whats-new/2025/04/whats-new-04-10-login-logout-audit.md": "43033",
   "/whats-new/2025/04/whats-new-2025-04-16": "43034",
   "/whats-new/2025/04/whats-new-04-23-otlp": "43035",
-  "/whats-new/2025/05/whats-new-05-06-log-table-settings": "43036"
+  "/whats-new/2025/05/whats-new-05-06-log-table-settings": "43036",
+  "/whats-new/2025/05/whats-new-05-19-change-tracking": "43037"
 }