Skip to content

build: relax Fable.Core pin to >= 5.0.0-rc.1#257

Merged
dbrattli merged 1 commit intomainfrom
chore/relax-fable-core-constraint
Apr 17, 2026
Merged

build: relax Fable.Core pin to >= 5.0.0-rc.1#257
dbrattli merged 1 commit intomainfrom
chore/relax-fable-core-constraint

Conversation

@dbrattli
Copy link
Copy Markdown
Collaborator

Summary

  • Change Fable.Core constraint in paket.dependencies from exact 5.0.0-rc.2 to >= 5.0.0-rc.1 lowest_matching: true (all three groups: Main, Test, Examples).
  • Paket's exact pin gets packed into the nupkg as [5.0.0-rc.2], which forced consumers on newer Fable.Core RCs into a resolver conflict. Switching to a minimum-version constraint matches how Fable.Browser.*, Fable.Promise, and Fable.Solid express their Fable.Core dependency.
  • Floor set at rc.1 (not rc.2) after confirming the bindings don't use any rc.2-specific API.

Test plan

  • just build succeeds
  • just test-python — 317/317 pass
  • paket.lock regenerated; Fable.Core resolves to rc.1 under lowest_matching
  • CI green

🤖 Generated with Claude Code

Changed from exact pin to minimum-version constraint so consumers on any
5.x Fable.Core (including newer RCs) can resolve Fable.Python without a
NuGet conflict. Verified build and all 317 Python tests pass against
Fable.Core 5.0.0-rc.1.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@dbrattli dbrattli merged commit deed5e7 into main Apr 17, 2026
9 checks passed
@dbrattli dbrattli deleted the chore/relax-fable-core-constraint branch April 17, 2026 05:23
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