• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

FlexMeasures / flexmeasures / 31784397478
84%

Build:
DEFAULT BRANCH: main
Ran 14 Aug 2026 08:43AM UTC
Jobs 1
Files 176
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Aug 2026 08:33AM UTC coverage: 84.085%. Remained the same
31784397478

push

github

web-flow
Pin and verify versions in published Docker images (#2425)

* Bake an explicit version into the Docker image

The version the UI footer reports comes from the installed package metadata, which hatch-vcs derives from .git when the image is built.
When the build context lacks the full history and tags, that silently yields a development version such as 1.0.0.dev127+g3d251777 instead of the released one.

Add a FLEXMEASURES_VERSION build arg that pins the version through SETUPTOOLS_SCM_PRETEND_VERSION, and pass the release tag to it when publishing.
The published image's version is then correct by construction, rather than dependent on how much history the checkout happened to fetch.
Verifying the pushed image afterwards turns a mislabelled release from a silent mistake into a failed build.

Leaving the arg empty keeps the previous behaviour of deriving the version from .git, so local and docker compose builds are unaffected.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Fetch full git history in the Docker build workflow

actions/checkout defaults to a shallow clone without tags, so hatch-vcs cannot resolve the version and bakes a development version into the image built here.
The QA workflow got this fix in #2263; this workflow was missed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Add changelog entry for the Docker image version fix

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* move this to v1.0, some more changelog fix-ups

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* reduce complexity of this PR to being a verification of the published version - we saw that the earlier error report was to blame on the developer (me) not pushing the tag correctly

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* pass release tags explicitly again, we encountered a problem with dirty git states leading to a new version

Signed-off-by: Nicolas Höning <nicolas@seita.nl>

* removve fetch-depth:0 which was not fully address... (continued)

17340 of 20622 relevant lines covered (84.08%)

0.84 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31784397478.1 14 Aug 2026 08:43AM UTC 176
84.08
GitHub Action Run
Source Files on build 31784397478
  • Tree
  • List 176
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #31784397478
  • 2c5736e7 on github
  • Prev Build on main (#31600114296)
  • Next Build on main (#31833786234)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc