-
Notifications
You must be signed in to change notification settings - Fork 142
Port dbt-metricflow package CI tests
#1933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
56e1854 to
e02c98c
Compare
754e9e1 to
1238a0b
Compare
tlento
left a comment
There was a problem hiding this 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 | |||
There was a problem hiding this comment.
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)?
38ef62a to
7ff4a4d
Compare
#1653 added a CI test for the
dbt-metricflowpackage in a release branch, but it's missing frommain. 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.