Skip to content

chore: bump pyfly to v26.06.113#66

Merged
miguelgfierro merged 3 commits into
mainfrom
chore/bump-pyfly-v26.06.113
Jun 19, 2026
Merged

chore: bump pyfly to v26.06.113#66
miguelgfierro merged 3 commits into
mainfrom
chore/bump-pyfly-v26.06.113

Conversation

@miguelgfierro

Copy link
Copy Markdown
Contributor

Summary

Upgrade the pyfly framework dependency to the latest published release v26.06.113.

Changes

  • [tool.uv.sources] pyfly git tag: v26.05.05v26.06.113
  • [project.dependencies] pyfly lower bound: >=26.5.4>=26.6.113
  • fireflyframework-agentic unchanged (v26.05.32) — resolves cleanly against the new pyfly, no bump required.
  • Added .worktrees/ to .gitignore.

Verification

  • uv lock resolves (327 packages).
  • uv sync clean.
  • Full test suite: 798 passed, 3 skipped.

(uv.lock is gitignored in this repo; CI regenerates it from the updated pin.)

Upgrade the pyfly dependency pin from v26.05.05 to the latest published
release v26.06.113, and raise the matching lower bound to >=26.6.113.
fireflyframework-agentic stays at v26.05.32 (resolves cleanly against the
new pyfly). Full test suite (798 passed, 3 skipped) green.
pyfly v26.06 splits actuator + admin onto a dedicated management port
(9090) by default. Collapse it onto the app port (8500) via
pyfly.management.server.port so /actuator/* health probes and /admin
stay reachable on the single business port (k8s probes, Taskfile, docs).
@miguelgfierro miguelgfierro merged commit 3dd55c2 into main Jun 19, 2026
6 checks passed
@miguelgfierro miguelgfierro deleted the chore/bump-pyfly-v26.06.113 branch June 19, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant