The producer hardcoded its version, so released artifacts reported a stale literal or -SNAPSHOT as the qbit's metadata version.
Fix: this follows the authentik pattern. A Maven-filtered qbit-web-performance.properties holds version=${project.version}, and the producer loads it. The tests assert that the producer version, the help bundle version and the artifact version are equal (surefire passes qbit.artifactVersion).
Codex notes:
Changed six files: pom.xml, WebPerfQBitProducer.java, new qbit-web-performance.properties, both producer/help-bundle tests, and CHANGELOG.md.
mvnw.cmd -q verify passed; one Docker-dependent test skipped.
RC.99 proof: all 7 tests passed with version 0.1.0-RC.99.
POM restored byte-for-byte, preserving ${revision} and only intended changes.
No commits or pushes.
Memory note staged in local cache; sandbox restrictions prevented writing to the vault.
The producer hardcoded its version, so released artifacts reported a stale literal or `-SNAPSHOT` as the qbit's metadata version.
**Fix:** this follows the authentik pattern. A Maven-filtered `qbit-web-performance.properties` holds `version=${project.version}`, and the producer loads it. The tests assert that the producer version, the help bundle version and the artifact version are equal (surefire passes `qbit.artifactVersion`).
**Codex notes:**
Changed six files: `pom.xml`, `WebPerfQBitProducer.java`, new `qbit-web-performance.properties`, both producer/help-bundle tests, and `CHANGELOG.md`.
- `mvnw.cmd -q verify` passed; one Docker-dependent test skipped.
- RC.99 proof: all 7 tests passed with version `0.1.0-RC.99`.
- POM restored byte-for-byte, preserving `${revision}` and only intended changes.
- No commits or pushes.
Memory note staged in local cache; sandbox restrictions prevented writing to the vault.
Low priority: this rides the repo's next RC.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The producer hardcoded its version, so released artifacts reported a stale literal or
-SNAPSHOTas the qbit's metadata version.Fix: this follows the authentik pattern. A Maven-filtered
qbit-web-performance.propertiesholdsversion=${project.version}, and the producer loads it. The tests assert that the producer version, the help bundle version and the artifact version are equal (surefire passesqbit.artifactVersion).Codex notes:
Changed six files:
pom.xml,WebPerfQBitProducer.java, newqbit-web-performance.properties, both producer/help-bundle tests, andCHANGELOG.md.mvnw.cmd -q verifypassed; one Docker-dependent test skipped.0.1.0-RC.99.${revision}and only intended changes.Memory note staged in local cache; sandbox restrictions prevented writing to the vault.
Low priority: this rides the repo's next RC.
🤖 Generated with Claude Code