Conversation
9ba12ef to
42c0a2e
Compare
42c0a2e to
975d0f2
Compare
|
Commit: 18341fd
15 interesting tests: 7 KNOWN, 7 SKIP, 1 flaky
Top 22 slowest tests (at least 2 minutes):
|
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
975d0f2 to
18341fd
Compare
| templatePathEnvVar = "DATABRICKS_APPKIT_TEMPLATE_PATH" | ||
| appkitRepoURL = "https://github.com/databricks/appkit" | ||
| appkitTemplateDir = "template" | ||
| appkitDefaultVersion = "v0.7.4" |
There was a problem hiding this comment.
The tag v0.7.4 points to AppKit package release. The template from that tag still uses 0.6.0 https://github.com/databricks/appkit/blob/1cf359641efca70abd287e6f4fd2c091a62fa713/template/package.json#L34-L35
We should use template-vx.y.z tag, but apparently we have some issues with the CI job that doesn't push them, so we'll need to push it manually.
The question is: does it mean you folks were evaluating the template with AppKit 0.6?
There was a problem hiding this comment.
Have we agreed when exactly we can bump the tag? What are the prerequisites to make sure it's the new default version?
|
@arsenyinfo can you rebase with main as we now have the --version have working properly, and make sure we point to a |
Summary
databricks apps initnow clones appkit tagv0.7.4instead ofmain--version lateststill points tomainbranch for bleeding edge--version <REF>and--branch <REF>work as beforeTest plan
go test ./cmd/apps/)--version latest→ clones main (41 files)--version v0.6.0→ clones v0.6.0 (41 files)--branch main→ clones main (41 files)🤖 Generated with Claude Code