gleam-lang/gleam

Gleam version with git hash

Open

#4544 opened on May 1, 2025

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

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

Tech stack
rust
Domain
clideveloper experience
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.
1-3 hours
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.
80
Research direction
Look at the current version output in the Gleam CLI, likely implemented in a file like `src/main.rs` or a version module. Modify the build script (e.g., `build.rs`) to include the git commit hash by executing `git rev parse short HEAD` during compilation. Then update the version string format to include the hash and date, similar to Cargo's output. This is a small, well defined task with clear examples in other Rust projects.