chore: bump locked dependencies (stdlib 1.0.5, exception 2.1.1) - #5
Open
maxh213 wants to merge 1 commit into
Open
chore: bump locked dependencies (stdlib 1.0.5, exception 2.1.1)#5maxh213 wants to merge 1 commit into
maxh213 wants to merge 1 commit into
Conversation
- gleam_stdlib 1.0.3 -> 1.0.5 - exception 2.1.0 -> 2.1.1 All 250 tests pass on Erlang and JavaScript targets after the update. No public API or constraint changes.
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.
Summary
Routine dependency lockfile update after
gleam deps update.Changes
gleam_stdlib1.0.3 → 1.0.5exception2.1.0 → 2.1.1Verification
gleam checkpassesgleam test— 250 passed (Erlang)gleam test --target javascript— 250 passedgleam_stdlib >= 0.44.0 and < 2.0.0unchanged)Rationale
Keeps the lockfile current with the latest patch releases of direct/transitive dependencies. The existing
latest-depsCI job already validates against newest versions; this simply records the current resolved set so local builds stay deterministic and up-to-date.No changelog entry required (internal lockfile only).