v0.5.18

[TNATALI]

Halo version v0.5.18 is now available as of May 2, 2025

##Highlights

• Support for sample interval wrapping. This will improve privacy budget utilization and can be enabled after HMSS is enabled (feat: Allow sampling interval wrapping around 1 #2207)
• Measurement Methodology is now required and Metrics are reported as failed if their variance cannot be computed (refactor: Metric State is set to FAILED when Measurement Result issues are present #2238 )
• The Noise Corrector now generates diagnostics and provides a mechanism for logging them to a storage bucket. (feat: Report post processor returns data quality proto. #2205 feat: Write noise correction log to storage. #2242)
• The Reporting API has new GetBasicReport and ListBasicReports methods (Implement GetBasicReport and ListBasicReports methods #2196). This completes MC API Phase I.
• These are supported by the new GetImpressionQualificationFilter and ListImpressionQualificationFilters methods (Implement ImpressionQualificationFilters service #2197)
• This requires a Cloud Spanner database. If you are using the reporting Terraform module, it will create one for you.
• To enable, set the --basic-reports-enabled option of the Reporting internal API server to true. When this option is true, the --impression-qualification-filter-config-file, --spanner-project, --spanner-instance, and --spanner-database options become required.
• The Reporting API has a new InvidateMetric method (Allow invalidation of Metrics #2195)
• This will set the Metric state to INVALID and prevent it from being reused by future Report resources.
• The state of Report resources that reference that Metric will be set to FAILED.
• The DataProvider resource in the CMMS API has a new data_availability_intervals field to specify the availability interval for each ModelLine (feat: Implement DataProviders/ReplaceDataAvailabilityIntervals #2188)
• This is intended to replace the singular data_availability_interval field.
• There is a corresponding ReplaceDataAvailabilityIntervals method.
• The EventGroup resource in the CMMS API has new event_group_metadata and media_types fields (Allow DataProviders to specify build number and warnings when fulfilling Requisitions #2190)
• While the event_group_metadata field is intended to eventually replace the metadata field, but both fields should continue to be populated until the field is deprecated.
• The Requisition resource in the CMMS API has a new fulfillment_context field (Allow DataProviders to specify build number and warnings when fulfilling Requisitions #2190)
• This allows DataProvider callers to specify a build label and warning information when fulfilling a Requistion.

##Bugs Addressed

• "Missing value for metric" error on ListReports #2108
• HMSS Variance is Reported as Zero #2198
• CreateReportingSet throws INVALID_ARGUMENT when rhs isn't set #2223

##For more informtion and details on what is included in the latest release, please visit:

• https://github.com/world-federation-of-advertisers/cross-media-measurement/releases/tag/v0.5.18