gleam-lang/gleam

Gleam version with git hash

Open

#4,544 opened on May 1, 2025

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Rust (960 forks)batch import
discussiongood first issuehelp wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (Avg merge 10d 19h) (69 merged PRs in 30d)

Description

If I run cargo --version i get to see the following:

cargo 1.86.0 (adf9b6ad1 2025-02-28)

I like to build from source, but I have no easy way to check which version I run exactly because i just get to see the latest tag 1.10.0. Is it possible to add a hash something similar to rust, so I can see wether I want to update or not?

Contributor guide

Research direction
Look at how the current version is printed (likely in src/main.rs or similar). Use the `git describe` or `git rev parse HEAD` at compile time via a build script to embed the commit hash. Alternatively, use the `vergen` crate. Modify the version output to include the hash, similar to cargo.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75