RustScan built from 2.4.1 tag reports version 2.3.0 due to outdated version in Cargo.toml
- Vorherrschende Sprache
- Rust
- Sterne
- 20.4k
- Forks
- 1.4k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
**Describe the bug**
When building RustScan from source using the 2.4.1 git tag, the resulting binary reports version 2.3.0 instead of 2.4.1.
**To Reproduce**
Steps to reproduce the behavior:
1. Clone the repository:
```bash
git clone https://github.com/bee-san/RustScan.git
cd RustScan
```
2. Checkout the 2.4.1 tag:
```bash
git checkout 2.4.1
```
3. Build the project:
```bash
cargo build --release
```
4. Check the version of the built binary:
```bash
./target/release/rustscan -V
```
5. The output is:
```
rustscan 2.3.0
```
**Expected behavior**
The binary built from the 2.4.1 tag should report version 2.4.1, not 2.3.0.
**Screenshots**
Not applicable.
**Desktop (please complete the following information):**
- OS: macOS 14.7.6 (23H626)
- Rust version: rustc 1.86.0 (05f9846f8 2025-03-31)
- Git version: git version 2.39.5 (Apple Git-154)
**Additional context**
This issue affects all builds from source, including Homebrew, which builds RustScan from the 2.4.1 tag and thus also produces a binary reporting version 2.3.0.
In the `Cargo.toml` file on the 2.4.1 tag, the version is still set to 2.3.0.
Please update the version in `Cargo.toml` before tagging and releasing new versions to avoid such inconsistencies.
Beitragsleitfaden
Rechercherichtung
Beginne mit Cargo.toml im 2.4.1-Tag und vergleiche dessen Version mit dem Tag-Namen. Baue mit cargo build --release und führe anschließend ./target/release/rustscan -V aus; fertig ist es, wenn die Binärdatei die Version 2.4.1 meldet.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- build-system, cli
- Issue-Typ
- Bug
- Schwierigkeit
- 1/5
- Geschätzter Aufwand
- Unter einer Stunde
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 52/100