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

chideat / valkey-operator / 34816127090
36%

Build:
DEFAULT BRANCH: main
Ran 14 Sep 2026 07:07AM UTC
Jobs 1
Files 147
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 Sep 2026 07:04AM UTC coverage: 26.442% (+0.007%) from 26.435%
34816127090

push

github

web-flow
fix: RC tags built Jan-Sep are invalid SemVer, leaving the operator inert (#124)

* fix(ci): RC tags built Jan-Sep are not valid SemVer, which disables the operator

branch-pipeline builds the release-candidate tag from a bare '+%m%d%H%M'
timestamp, so a build on 12 Sep 15:29 produces:

  v2.0.0-rc.09121529.d812ee9

SemVer forbids leading zeros in numeric pre-release identifiers, so 09121529
makes the whole version unparseable. ActorManager.Search parses that version to
pick a versioned actor, and on failure returns nil for *every* command:

  ver, _ := semver.NewVersion(crVersion)
  if ver == nil { return nil }

The operator therefore never runs a single actor. It creates no StatefulSets,
and every reconcile logs

  actor for command not register: unknown command CommandUpdateAccount

which points at actor registration rather than at the version string that
actually broke. Verified on a live cluster: cluster and failover instances both
sat at Initializing indefinitely. Re-tagging the identical image manifest
(amd64 sha256:65436fda2873...) with a parseable version and upgrading in place
brought both to Ready with no change to the CRs.

The defect is seasonal, which is why it went unnoticed: only months 01-09 carry
a leading zero, so builds made in October, November and December are fine. It
has been latent for every Jan-Sep build since the '-rc.${TS}.' tag shape was
introduced. Final release tags (v2.0.0) are unaffected -- they have no
pre-release part.

Prefixing the timestamp with %Y fixes it, because a four-digit year can never
start with a zero, and the tag gains the year it was missing.

The test reads the format out of the workflow instead of restating it, so the
two cannot drift apart, and checks one sample per month rather than only the
current date -- otherwise it would pass for a quarter of the year regardless.

* fix(actor): log the version parse error instead of discarding it

Search discarded the error from semver.NewVersion and returned ... (continued)

2 of 4 new or added lines in 1 file covered. (50.0%)

5491 of 20766 relevant lines covered (26.44%)

0.3 hits per line

Uncovered Changes

Lines Coverage ∆ File
2
91.01
-2.09% internal/actor/manager.go
Jobs
ID Job ID Ran Files Coverage
1 34816127090.1 14 Sep 2026 07:07AM UTC 147
26.44
GitHub Action Run
Source Files on build 34816127090
  • Tree
  • List 147
  • Changed 2
  • Source Changed 0
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • d555f541 on github
  • Prev Build on main (#34698319084)
  • Next Build on main (#34821160671)
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