ci: Add datasqrl-examples bump and validation workflows#2075
Conversation
…on release Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2075 +/- ##
=========================================
Coverage 13.35% 13.35%
Complexity 841 841
=========================================
Files 606 606
Lines 17516 17516
Branches 2122 2122
=========================================
Hits 2340 2340
Misses 14960 14960
Partials 216 216 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
…ircleCI Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
ferenc-csaky
left a comment
There was a problem hiding this comment.
I don't think this should be executed for every PR or commit that makes it into main.
Ideally that would be nice, but IMO in real life that will be just another annoying step we just skip most of the time, and will be red until we release anyways.
WDYT?
well, if we don't run this on every PR, we will only know it's broken after someone manually checks |
datasqrl-examples bump and validation workflows
Summary
datasqrl-examplesagainst a selected SQRL CLI image.datasqrl/cmd:dev, while still allowing maintainers to pass snapshot images likeghcr.io/datasqrl/cmd:pr-123.DataSQRL/datasqrl-examplesbuild.yml, locate the downstream run bycorrelation_id, and wait for it to finish.datasqrl-examplesvalidation detached from CircleCI instead of running it as a CircleCI job.pr-*tags so they can be manually validated by the examples workflow.datasqrl-examplesto bump itsSQRL_VERSION.EXAMPLES_BOT_PATsecret for cross-repo examples operations.