Skip to content

chore(lakebase): set package version to 0.2.0 for CI registry#336

Merged
MarioCadenas merged 1 commit intomainfrom
chore/downgrade-lakebase-0.2
Apr 30, 2026
Merged

chore(lakebase): set package version to 0.2.0 for CI registry#336
MarioCadenas merged 1 commit intomainfrom
chore/downgrade-lakebase-0.2

Conversation

@MarioCadenas
Copy link
Copy Markdown
Collaborator

Downgrade packages/lakebase from 0.3.0 to 0.2.0 so the packed @databricks/appkit tarball declares a @databricks/lakebase version that resolves on the CI npm registry (JFrog). 0.3.0 was not available there, which broke prepare-release when the template-artifact job runs npm install.

@MarioCadenas MarioCadenas changed the title deps(lakebase): set package version to 0.2.0 for CI registry chore(lakebase): set package version to 0.2.0 for CI registry Apr 30, 2026
@MarioCadenas MarioCadenas force-pushed the chore/downgrade-lakebase-0.2 branch from faee329 to b068899 Compare April 30, 2026 15:53
Downgrade from 0.3.0 so the packed @databricks/appkit tarball declares a
@databricks/lakebase version that resolves on JFrog during prepare-release
template-artifact npm install.
@MarioCadenas MarioCadenas force-pushed the chore/downgrade-lakebase-0.2 branch from b068899 to c1dd746 Compare April 30, 2026 15:56
@MarioCadenas MarioCadenas enabled auto-merge (squash) April 30, 2026 15:56
@MarioCadenas MarioCadenas merged commit 8e174db into main Apr 30, 2026
8 checks passed
@MarioCadenas MarioCadenas deleted the chore/downgrade-lakebase-0.2 branch April 30, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants