feat(api): aggregated API specs update

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 612
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/gcore%2Fgcore-308c971e681f1c4d36c47ee545e002a364e4491797694a069f3b4cddc9202347.yml
-openapi_spec_hash: e579cb5c51a08bb69634651da66148ac
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/gcore%2Fgcore-5a7ab6a73d8b5baaf7f48ba5dc59aab2288689470607e793205aafe92a0ae48f.yml
+openapi_spec_hash: bb229625bc538d51d91bd2edffa2048f
 config_hash: 399dda838c78c5d92532b7efcaaa0345

src/gcore/resources/cloud/cost_reports.py

@@ -110,12 +110,11 @@ def get_aggregated(
         /v1/`reservation_cost_report`/totals, as the results from this report will not
         be accurate.
 
-        Receiving data from the past hour might lead to incomplete statistics. For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        Data from the past hour may not reflect the full set of statistics. For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           time_from: The start date of the report period (ISO 8601). The report starts from the
@@ -226,12 +225,11 @@ def get_aggregated_monthly(
         spent billing units (e.g., hours or GB) for resources. The "`time_to`" parameter
         represents all days in the specified month.
 
-        Receiving data from the past hour might lead to incomplete statistics. For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        Data from the past hour may not reflect the full set of statistics. For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           regions: List of region IDs.
@@ -344,12 +342,11 @@ def get_detailed(
         /v1/`reservation_cost_report`/totals, as the results from this report will not
         be accurate.
 
-        Receiving data from the past hour might lead to incomplete statistics. For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        Data from the past hour may not reflect the full set of statistics. For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           time_from: The start date of the report period (ISO 8601). The report starts from the
@@ -495,12 +492,11 @@ async def get_aggregated(
         /v1/`reservation_cost_report`/totals, as the results from this report will not
         be accurate.
 
-        Receiving data from the past hour might lead to incomplete statistics. For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        Data from the past hour may not reflect the full set of statistics. For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           time_from: The start date of the report period (ISO 8601). The report starts from the
@@ -611,12 +607,11 @@ async def get_aggregated_monthly(
         spent billing units (e.g., hours or GB) for resources. The "`time_to`" parameter
         represents all days in the specified month.
 
-        Receiving data from the past hour might lead to incomplete statistics. For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        Data from the past hour may not reflect the full set of statistics. For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           regions: List of region IDs.
@@ -729,12 +724,11 @@ async def get_detailed(
         /v1/`reservation_cost_report`/totals, as the results from this report will not
         be accurate.
 
-        Receiving data from the past hour might lead to incomplete statistics. For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        Data from the past hour may not reflect the full set of statistics. For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           time_from: The start date of the report period (ISO 8601). The report starts from the

src/gcore/resources/cloud/usage_reports.py

@@ -95,14 +95,13 @@ def get(
         extra_body: Body | None = None,
         timeout: float | httpx.Timeout | None | NotGiven = not_given,
     ) -> UsageReport:
-        """Receiving data from the past hour might lead to incomplete statistics.
+        """Data from the past hour may not reflect the full set of statistics.
 
-        For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           time_from: The start date of the report period (ISO 8601). The report starts from the
@@ -233,14 +232,13 @@ async def get(
         extra_body: Body | None = None,
         timeout: float | httpx.Timeout | None | NotGiven = not_given,
     ) -> UsageReport:
-        """Receiving data from the past hour might lead to incomplete statistics.
-
-        For the
-        most accurate data, we recommend accessing the statistics after at least one
-        hour. Typically, updates are available within a 24-hour period, although the
-        frequency can vary. Maintenance periods or other exceptions may cause delays,
-        potentially extending beyond 24 hours until the servers are back online and the
-        missing data is filled in.
+        """Data from the past hour may not reflect the full set of statistics.
+
+        For the most
+        complete and accurate results, we recommend accessing the data at least one hour
+        after the relevant time period. Updates are generally available within a 24-hour
+        window, though timing can vary. Scheduled maintenance or other exceptions may
+        occasionally cause delays beyond 24 hours.
 
         Args:
           time_from: The start date of the report period (ISO 8601). The report starts from the