Repository navigation
chore(release): 1.7.8 — Terraform conformance, grants, admin belt - #20
Merged
Merged
Conversation
Bumps the version and brings the user-facing surfaces in line with what 1.7.8 ships. site/index.html gains the three service groups added since 1.7.7 — UC grants, workspace admin and legacy SQL — and its hero stats are refreshed (21+ -> 30+ API groups, 338+ -> 378+ tests). The Terraform feature card now says the claim is verified on every test run rather than merely asserted, which is the substantive change in this release. README.md was already updated alongside the code in #19, so it needs no correction here; this is the first release where the docs did not drift. Version updated in pyproject.toml, uv.lock, FEATURES.md and the site's version badge; CHANGELOG.md gains the 1.7.8 entry. The runtime version comes from package metadata, so pyproject.toml remains the only source. The changelog leads with the reachable-surface figure (267 of 564, ~47%) rather than the raw 22.9%, because 604 of the missing endpoints are in blocks this project deliberately skips and counting them makes progress look permanently hopeless. Publishing note: .github/workflows/pages.yml triggers only on site/**, so this is the commit that redeploys the page.
dmux
added
documentation
Owner
Author
|
LGTM! 🚀 |
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
1 participant
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.
Release PR for the work in #19.
Version
1.7.7 → 1.7.8 in
pyproject.toml,uv.lock,FEATURES.mdand the site's versionbadge, plus the
CHANGELOG.mdentry. The runtime version is read from packagemetadata, so
pyproject.tomlremains the only source — the rest is prose.Verified:
from minilake import __version__→1.7.8, and no1.7.7remains outsideCHANGELOG history and the compare links.
Site
README.mdwas updated alongside the code in #19, so unlike the last two releases therewas nothing to correct here — no stale or false claims. The site still needed catching
up, since #19 did not touch
site/:workspace admin use the
Unenforced CRUDpill, because that is what they are.provider is driven through
apply,plananddestroy, and a second plan has tocome back empty. That is the substantive change in this release, and the card
previously asserted what nothing checked.
instead.
A note on the number in the changelog
The entry leads with 267 of 564 reachable endpoints (~47%) rather than the raw
22.9%. 604 of the "missing" endpoints are in blocks this project has deliberately
decided not to emulate — MLflow, the Account API, identity v2, marketplace, Genie,
Lakebase, vector search, serving, clean rooms, apps. Counting those as gaps makes
progress look permanently hopeless and hides which gaps are real.
Verification
site/index.htmlparsestests running against the baked provider mirror
docker compose -f docker-compose.test.yml down -vafterPublishing
.github/workflows/pages.ymltriggers only onsite/**, so merging this is whatredeploys the page.
docs/is still not published to Pages — the coverage map androadmap remain GitHub-rendered markdown linked from the README.
After merge: tag
v1.7.7-style (git tag v1.7.8 && git push origin v1.7.8) to buildthe image, publish to PyPI and create the GitHub Release.