Skip to content

Conversation

@plypaul
Copy link
Contributor

@plypaul plypaul commented Nov 10, 2025

#1653 added a CI test for the dbt-metricflow package in a release branch, but it's missing from main. Note that due to naming update, dbt-metricflow's dependencies needs to be updated with a new release of MF, so this PR needs to be updated and merged only after the new release is available.

@plypaul plypaul force-pushed the p/fix_cli_logging__01 branch from 56e1854 to e02c98c Compare November 10, 2025 18:38
@plypaul plypaul force-pushed the p/fix_cli_logging__02 branch from 754e9e1 to 1238a0b Compare November 10, 2025 18:38
@plypaul plypaul marked this pull request as ready for review November 10, 2025 18:45
@plypaul plypaul requested a review from a team as a code owner November 10, 2025 18:45
Copy link
Contributor

@tlento tlento left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems reasonable but I don't have full context on these package tests. Might be good to chat briefly just so I can get up to speed.

@@ -1 +1 @@
metricflow==0.209.0
metricflow @ git+https://github.com/dbt-labs/metricflow.git@a430e4c2aeb77fe18d1c876326ef54ccf1cd464f
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the description, we don't want to merge like this, right? So this would be updated once the 0.210 or whatever release is deployed and then we'd roll this out with 0.211 (although since this is a package test it'll continue to run in the interim)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants