Repository navigation
chore(release): 1.7.7 — docs sync and version bump - #18
Merged
Merged
Conversation
Bumps the version and brings the user-facing docs in line with what 1.7.7 actually ships. README.md and site/index.html both carried statements that stopped being true when the coverage work landed: - Identity was described as a static current-user endpoint; it is now full SCIM CRUD for users, groups and service principals. - Secret scope ACLs were listed under "not implemented" (README listed them twice — in the 501 row and again under Known Gaps); they are implemented. Both now also list the services added since 1.7.6 — alerts, tokens, cluster policies, instance pools, UC functions and the metastore reads — and the site's hero stats are refreshed (16+ -> 21+ API groups, 138+ -> 338+ tests). The README's authentication gap now says plainly that SCIM identities and personal access tokens are records rather than credentials, so nobody reads the new endpoints as a way to sign in. Version updated in pyproject.toml, uv.lock, FEATURES.md and the site's version badge; CHANGELOG.md gains the 1.7.7 entry. The runtime version comes from package metadata, so pyproject.toml is the only source. Publishing note: .github/workflows/pages.yml only triggers on site/**, so this is the commit that redeploys the page. docs/ is not published to Pages -- the coverage map and roadmap are GitHub-rendered markdown, linked from README and docs/index.md.
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
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.
Follow-up to #17. That PR added services but only updated
FEATURES.mdanddocs/— the two user-facing surfaces were left behind, and both ended upstating things that are no longer true.
Corrections
Not just additions — these were wrong on
main:Identity (SCIM)· Static · "Fake current-user endpoint"Secrets ACLsas not implementedsite/index.htmlIdentity (SCIM)· Static · "A fixed current-user endpoint"Additions
Both surfaces now list what shipped since 1.7.6: alerts, tokens, cluster
policies, instance pools, UC functions, and the metastore reads. Jobs mentions
runs/submitand thatsql_task.file/.query/.alertall execute for real.Clusters mentions
update/pin/unpin.The README's authentication gap now says plainly that SCIM identities and
personal access tokens are records, not credentials — creating a user makes
no way to sign in, and revoking a token locks nobody out. Worth being explicit
about, since a table row reading "Identity & SCIM · Real CRUD" invites exactly
the wrong inference.
New rows use an
Unenforced CRUDpill on the site for the three groups thatare real CRUD but constrain nothing: identity, tokens, and policies/pools.
Hero stats refreshed: 16+ → 21+ API groups (the registry went from 12 to 17
real services, and 21 is also the measured count of
databricksCLI commandgroups that now work end-to-end), 138+ → 338+ tests.
Version
1.7.6 → 1.7.7 in
pyproject.toml,uv.lock,FEATURES.md, and the site'sversion badge, plus a
CHANGELOG.mdentry. The runtime version is read frompackage metadata (
importlib.metadata.version), sopyproject.tomlis theonly source — the rest are prose.
Publishing
.github/workflows/pages.ymltriggers only onsite/**, so #17 neverredeployed the page — nothing was broken, the site simply still described the
previous release. This commit touches
site/, so merging it publishes.Worth knowing:
docs/is not published to Pages; onlysite/is. Thecoverage map and roadmap are GitHub-rendered markdown, linked from the README
and
docs/index.md. Putting the coverage numbers on the public site would be aseparate decision — they would then need regenerating every release, or they
become one more thing that quietly goes stale.
Verification
uv run python -c "from minilake import __version__; print(__version__)"→1.7.71.7.6left outside CHANGELOG history and the compare linkssite/index.htmlparses