Repository navigation
chore(release): 1.7.2 — declare pytz as a runtime dependency - #11
Merged
Merged
Conversation
Dependency-only release: pytz is now declared as a runtime dependency. Nothing in the tree pulled it in, so it was simply absent from an install. Job and notebook containers run from their own images and do not install the wheel, so they are unaffected by this. Claude-Session: https://claude.ai/code/session_01FUPTtncD4ivN3YbQ6peNV2
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.
Dependency-only release. No behaviour changes.
What
pyproject.toml: addspytz>=2024.1to[project].dependenciesand bumpsversionto1.7.2.uv.lock: relocked (uv lock) — resolvespytz 2026.3.post1.CHANGELOG.md: new[1.7.2]section plus the compare link.FEATURES.md: version/date header.site/index.html: the version badge on the GitHub Pages landing page,v1.7.1→v1.7.2. Merging this tomaintriggers thePagesworkflow, which redeploys https://dmux.github.io/minilake/ automatically.Why
minilake's own modules use the standard library for time zones (
datetime.timezoneintls.py,services/files.py,services/saved_queries.py).pytzwas not in the dependency tree at all, so code running against an install — notebooks and scripts handling timezone-aware data — could not rely on it being there.pip install minilakenow brings it.Scope note: this covers the Python environment minilake is installed into. Job and notebook containers run from their own images (
MINILAKE_SPARK_IMAGE,Dockerfile.notebook) and do not install the wheel, so they do not inherit this dependency.Verification
uv sync+uv run python -c "import pytz"→2026.3.post1uv build --wheel→ the 1.7.2 wheel's METADATA carriesRequires-Dist: pytz>=2024.1docker-compose.test.yml) → 264 passed in 73suv run ruff check src/ tests/→ cleanrelease.yml:28-37) —grep -m1 '^version = ' pyproject.toml→1.7.2https://claude.ai/code/session_01FUPTtncD4ivN3YbQ6peNV2