Repository navigation
chore(release): 1.7.6 - #15
Merged
Merged
Conversation
Retargets the 1.7.5 release, which was prepared on main (commit 0712860) but never tagged or published — so no v1.7.5 exists on PyPI, GHCR, or GitHub Releases, and ghcr.io/dmux/minilake:latest is still the 1.7.4-era build. 1.7.6 is the first published build carrying those fixes; no code changes since 1.7.5's prep. Contents (unchanged from the 1.7.5 prep): four Workspace/Jobs API fixes for the Databricks VS Code extension and bundle CLI against minilake — workspace/export honors direct_download (fixes "lineage mismatch in state files" on repeated bundle deploy/run), runs/get and runs/list populate run_page_url, /Users/<user> is created on startup with directories carrying an object_id, and workspace/import accepts AUTO as an alias for SOURCE. No API changes beyond those fixes; no behaviour change for plain SQL/UC workloads. Claude-Session: https://claude.ai/code/session_01Ls8HmpdQGYwZbknVPMvAD2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retargets the 1.7.5 release, which was prepared on
main(commit0712860,chore(release): 1.7.5) but never tagged or published:v1.7.5git tagpypi.org/pypi/minilake/1.7.5/json→ 404; releases stop at 1.7.4)ghcr.io/dmux/minilake:1.7.5imageso
ghcr.io/dmux/minilake:latestis still the 1.7.4-era build (2026-09-01) andbundle deployagainst minilake keeps failing withlineage mismatch in state files.1.7.6 is the first published build carrying the 1.7.5 fixes. No code changes since that prep — this PR is only the version bump (
pyproject.toml,uv.lock,site/index.html,FEATURES.md) and retargeting the CHANGELOG section[1.7.5]→[1.7.6]+ its compare link.Contents shipped (from the 1.7.5 prep, all already on
main):workspace/exporthonorsdirect_download→ fixes repeatedbundle deploy/runruns/get/runs/listpopulaterun_page_url/Users/<user>created on startup; directories get anobject_idworkspace/importacceptsAUTOas an alias forSOURCEAfter merge: tag
v1.7.6on the merge commit and push → Release workflow publishes GHCR + PyPI + GitHub Release.https://claude.ai/code/session_01Ls8HmpdQGYwZbknVPMvAD2