Skip to content

Bump Gleam version to v.1.14#298

Open
selwynsimsek wants to merge 12 commits intoniklas-heer:masterfrom
selwynsimsek:master
Open

Bump Gleam version to v.1.14#298
selwynsimsek wants to merge 12 commits intoniklas-heer:masterfrom
selwynsimsek:master

Conversation

@selwynsimsek
Copy link
Contributor

@selwynsimsek selwynsimsek commented Feb 22, 2026

This change uses the new version v.1.14 of Gleam that was released on December 25, 2025.

Using v.1.13 (as we do currently) causes the benchmark CI workflow to fail, see e.g. a log.

This should hopefully fix the CI which has been broken since then, though I haven't tested the CI myself.

I saw there were some other PRs that discussed updating Gleam, #263 and #292, neither of which were merged.

I decided to make a PR for this manually since I suspect the automated bot got confused because it already made a request in #263 which was then superseded by #292 which was then closed anyway.

As using v.1.13 breaks the speed comparison it seems important to sort out.

Summary by CodeRabbit

  • Chores
    • Updated build infrastructure to use Gleam version 1.14.0.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 22, 2026

No actionable comments were generated in the recent review. 🎉


Walkthrough

Updated Gleam package version from 1.13.0 to 1.14.0 in two configuration files: the Earthfile Docker image reference and the dagger-poc language configuration.

Changes

Cohort / File(s) Summary
Gleam version updates
Earthfile, dagger-poc/languages.py
Bumped Gleam version from 1.13.0 to 1.14.0 in the base Docker image and nixpkgs language configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Bump Gleam version to v.1.14' directly and clearly summarizes the main change: updating Gleam from v1.13.0 to v1.14.0 across both the Earthfile and dagger-poc/languages.py.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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