[Bug] The version constant says 0.2.0 while the release is called 0.1.0 #629

New issue

Closed

opened 2026-07-22 16:21:55 +00:00 by brenno · 0 comments

brenno commented

2026-07-22 16:21:55 +00:00

Owner

Found in the pre-publication claim audit. Belongs with #520 (release engineering) but is filed separately so it can be ticked off on its own.

Evidence: pubspec.yaml:4 — version: 0.2.0+1; lib/services/export_metadata.dart:18 — const kOciDeckVersion = "0.2.0", which feeds :21 kOciDeckProducer (the Producer/Creator field written into every exported PDF and PPTX) and the About panel (lib/widgets/dialogs/parts/settings_dialog_about.dart:331). test/version_consistency_test.dart:21 locks the two together, so the constant is not a stray — the pair is guarded, the prose is not.

Against the stated intent to publish 0.1.0: COMPLIANCE.md:65 "Valid for versions: The default branch. There are no releases and no version tags"; :68 "pubspec.yaml carries 0.2.0+1, but that changes only when someone bumps it"; COMPLIANCE.md:130 BR.02 "No releases exist, so there is nothing to version"; docs/FAQ.md:33-34 "There is, however, nothing to download yet." And docs/FILE_FORMAT.md writes "as of 0.1.0" in thirteen places as though it already exists.

Why this matters now: if 0.1.0 ships, every PDF and PPTX it exports carries OciDeck 0.2.0 in its metadata — in the artefacts a penetration-test client keeps — and the About panel disagrees with the tag. It also breaks COMPLIANCE.md BR.02 "monotonically increasing" in the wrong direction: 0.2.0 would already exist in the field before 0.1.0.

Proposal: pick the number, set pubspec.yaml and kOciDeckVersion to it in one commit, and in the same commit flip the sentences that assume no release exists: COMPLIANCE.md:65, :68, :130-140, docs/FAQ.md:33-34, and the README doc-table row at README.md:128.

Found in the pre-publication claim audit. Belongs with #520 (release engineering) but is filed separately so it can be ticked off on its own. **Evidence:** `pubspec.yaml:4` — `version: 0.2.0+1`; `lib/services/export_metadata.dart:18` — `const kOciDeckVersion = "0.2.0"`, which feeds `:21` `kOciDeckProducer` (the Producer/Creator field written into every exported PDF and PPTX) and the About panel (`lib/widgets/dialogs/parts/settings_dialog_about.dart:331`). `test/version_consistency_test.dart:21` locks the two together, so the constant is not a stray — the pair is guarded, the prose is not. Against the stated intent to publish 0.1.0: `COMPLIANCE.md:65` "Valid for versions: **The default branch.** There are no releases and no version tags"; `:68` "`pubspec.yaml` carries `0.2.0+1`, but that changes only when someone bumps it"; `COMPLIANCE.md:130` BR.02 "**No releases exist**, so there is nothing to version"; `docs/FAQ.md:33-34` "There is, however, **nothing to download yet**." And `docs/FILE_FORMAT.md` writes "as of 0.1.0" in thirteen places as though it already exists. **Why this matters now:** if 0.1.0 ships, every PDF and PPTX it exports carries `OciDeck 0.2.0` in its metadata — in the artefacts a penetration-test client keeps — and the About panel disagrees with the tag. It also breaks COMPLIANCE.md BR.02 "monotonically increasing" in the wrong direction: 0.2.0 would already exist in the field before 0.1.0. **Proposal:** pick the number, set `pubspec.yaml` and `kOciDeckVersion` to it in one commit, and in the same commit flip the sentences that assume no release exists: `COMPLIANCE.md:65`, `:68`, `:130-140`, `docs/FAQ.md:33-34`, and the README doc-table row at `README.md:128`.

brenno added the

bug

label

2026-07-22 16:21:55 +00:00

brenno referenced this issue from a commit

2026-07-22 18:07:01 +00:00

fix: zet de versie op 0.1.0, en meet de prestatietest op de snelste

brenno referenced this issue from a pull request that will close it,

2026-07-22 18:07:02 +00:00

fix: versie naar 0.1.0, en de prestatietest op de snelste meten (#629, #638) #664

brenno closed this issue

2026-07-22 18:07:15 +00:00