chore: upgrade fable-library to 5.13, Fable.Beam to rc.34 - #36
Merged
Conversation
Bumps the Python runtime dependency from fable-library 5.11.0 to 5.13.0 in both pyproject.toml files, with the lockfiles relocked to match. The library's Fable.Beam reference already floats on 5.0.0-rc.*, so it picks up rc.34 (the latest published) without an edit; the timeflies BEAM example pinned rc.30 and is moved to rc.34 so both build against the same backend. Fable.Beam.Cowboy rc.24 is still the latest published and stays put. The Fable CLI tool was already pinned at 5.13.0. No source changes were needed — nothing in the toolchain broke this time. Verified: 28/28 tests pass on .NET, Python, JS and BEAM; `just build` compiles the library to Erlang and through rebar3; both the timeflies BEAM and Python examples build. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Bumps the Python runtime dependency from
fable-library5.11.0 to 5.13.0 in bothpyproject.tomlfiles, with the lockfiles relocked to match.The library's
Fable.Beamreference already floats on5.0.0-rc.*, so it picks up rc.34 (the latest published) without an edit — confirmed inproject.assets.json. The timeflies BEAM example pinned rc.30 and is moved to rc.34 so both build against the same backend.Fable.Beam.Cowboyrc.24 is still the latest published and stays put. The Fable CLI tool was already pinned at 5.13.0.No source changes were needed — nothing in the toolchain broke this time.
Changes
pyproject.tomlfable-library>=5.11.0→>=5.13.0uv.lockexamples/timeflies-python/pyproject.toml+uv.lockexamples/timeflies-beam/src/Timeflies.fsprojFable.Beamrc.30 → rc.34CLAUDE.mdThe large lockfile diffs are entirely the per-platform wheel hash list for the new
fable-libraryversion.Verification
just check— cleanjust test— 28/28 passing on all four targets (.NET, Python, JS, BEAM)just build— Erlang codegen + rebar3 compile clean (only the pre-existingseq.erl/fable_actor_platform.erlunused-term warnings)just build-timeflies— compiles under rc.34just build-timeflies-python— compiles against fable-library 5.13🤖 Generated with Claude Code