chore(release): phlo 0.8.0 + 3 packages

[iamgp]

Release summary

[phlo 0.8.0 + 3 packages] - 2026-04-07

Added

• phlo: pymdx driven docs (feat: pymdx driven docs #327)

Fixed

• phlo: add manual release publish trigger
• phlo: accept bare version in manual release trigger
• phlo: gather remaining release artifacts into root dist
• phlo: simplify release publish and disable docs workflow
• phlo: keep docs
• phlo: clean deploy gh-pages, preserve cairn, move pymdx to dev deps
• phlo: inject basePath into next.config for GitHub Pages
• phlo: resolve pandera mutation, null column loop, hardcoded version, plugin registration (fix: resolve pandera mutation, null column loop, hardcoded version, plugin registration #357)
• phlo: security hardening — SQL injection, timing attacks, path traversal, stub reverts (fix: security hardening — SQL injection, timing attacks, path traversal, stub reverts #358)
• phlo: dev mode production guard, command injection, hardcoded creds, auth logging, CLI fixes (fix: dev mode production guard, command injection, hardcoded creds, auth logging, CLI fixes #359)
• phlo: correctness fixes, dead code removal, and security hardening (fix: correctness fixes, dead code removal, and security hardening #360)
• phlo: security hardening and config correctness (fix: security hardening and config correctness #362)
• phlo: CLI and plugin system correctness fixes (fix: CLI and plugin system correctness fixes #361)
• phlo: correct 4 CLI correctness issues from batch [MEDIUM] CLI correctness issues batch #347 (fix(cli): correct 4 CLI correctness issues from batch #347 #364)
• phlo: normalize tags dict in HookFilter.post_init (fix(plugins): normalize tags dict in HookFilter.__post_init__ #365)
• phlo: prevent info leak from exception cause chain (fix(exceptions): prevent info leak from exception cause chain #366)
• phlo: proxy auth signing and project root resolution (fix: proxy auth signing and project root resolution #367)
• phlo-dbt: security hardening — SQL injection, timing attacks, path traversal, stub reverts (fix: security hardening — SQL injection, timing attacks, path traversal, stub reverts #358)
• phlo-dbt: dev mode production guard, command injection, hardcoded creds, auth logging, CLI fixes (fix: dev mode production guard, command injection, hardcoded creds, auth logging, CLI fixes #359)
• phlo-dlt: resolve pandera mutation, null column loop, hardcoded version, plugin registration (fix: resolve pandera mutation, null column loop, hardcoded version, plugin registration #357)
• phlo-pandera: correctness fixes, dead code removal, and security hardening (fix: correctness fixes, dead code removal, and security hardening #360)

Contributors

Thanks to our contributors for this release:

• @iamgp (25 commits)

Maintainer checklist

• Review version bump
• Review changelog
• Merge to cut the release

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Greptile Summary

This is a standard release PR that bumps the phlo package version from 0.7.10 to 0.7.11. All version references are updated consistently across the codebase.

• CHANGELOG.md: New entry added for 0.7.11 documenting the fix for the manual release publish trigger
• pyproject.toml: version field updated to 0.7.11
• src/phlo/cli/__init__.py: __version__ updated to 0.7.11
• src/phlo/plugins/__init__.py: __version__ updated to 0.7.11
• uv.lock: Lock file updated to reflect the new package version

All version strings are consistent across files. No logic changes are introduced — this is purely a version bump release.

Confidence Score: 5/5

This PR is safe to merge — it is a mechanical version bump with no logic changes.

All five changed files are updated consistently to version 0.7.11, the changelog entry matches the PR description, and there are no code logic changes introduced. The only risk would be an inconsistent version string, which is not present here.

No files require special attention.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds new changelog entry for phlo 0.7.11 with fix description for the manual release publish trigger
pyproject.toml	Version bumped from 0.7.10 to 0.7.11 — consistent with changelog and other files
src/phlo/cli/init.py	__version__ bumped from 0.7.10 to 0.7.11, consistent with the release
src/phlo/plugins/init.py	__version__ bumped from 0.7.10 to 0.7.11, consistent with the release
uv.lock	Lock file updated to reflect the new phlo version 0.7.11

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR #326: phlo 0.7.11 Release] --> B[CHANGELOG.md\nAdd 0.7.11 entry]
    A --> C[pyproject.toml\n0.7.10 → 0.7.11]
    A --> D[src/phlo/cli/__init__.py\n__version__ 0.7.10 → 0.7.11]
    A --> E[src/phlo/plugins/__init__.py\n__version__ 0.7.10 → 0.7.11]
    A --> F[uv.lock\nphlo 0.7.10 → 0.7.11]
    B & C & D & E & F --> G[Release: phlo 0.7.11]

Loading

_{Reviews (1): Last reviewed commit: "chore(release): phlo 0.7.11" | Re-trigger Greptile}

[github-actions]

Cairn Quality Report

Commit: 0c4750e · View full report

Checker	Status	✅ Passed	❌ Failed	Items
ruff	passed	0	0	0
ruff-format	pass	0	0	1
pytest-3.11	passed	410	0	411
pytest-3.12	passed	410	0	411

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🟡 phlo-pandera version in init.py not updated to match pyproject.toml bump

The PR bumps packages/phlo-pandera/pyproject.toml version from 0.2.3 to 0.2.4, but the corresponding __version__ string in packages/phlo-pandera/src/phlo_pandera/__init__.py:170 is still "0.2.3". This means phlo_pandera.__version__ will report 0.2.3 at runtime while the installed package metadata says 0.2.4. The main phlo package correctly updates __version__ in both src/phlo/cli/__init__.py and src/phlo/plugins/__init__.py, so this appears to be an oversight specific to phlo-pandera.

Prompt for agents

The phlo-pandera pyproject.toml version was bumped from 0.2.3 to 0.2.4, but the __version__ variable in packages/phlo-pandera/src/phlo_pandera/__init__.py (line 170) still reads "0.2.3". Update it to "0.2.4" to match the pyproject.toml. Also update the docstring reference on line 107 of the same file which mentions "0.2.3" as the example version string.

---

Was this helpful? React with 👍 or 👎 to provide feedback.