Skip to content

chore(deps): update module github.com/scality/raidmgmt to v0.20.0 - #111

Open
scality-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-scality-raidmgmt-0.x
Open

scality-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-scality-raidmgmt-0.x

Conversation

@scality-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/scality/raidmgmt v0.14.0 → v0.20.0 age adoption passing confidence

Release Notes

scality/raidmgmt (github.com/scality/raidmgmt)

v0.20.0

Compare Source

What's Changed

New Contributors

Full Changelog: v0.19.0...v0.20.0

v0.19.0

Compare Source

What's Changed

Full Changelog: v0.18.1...v0.19.0

v0.18.1

Compare Source

What's Changed

Full Changelog: v0.18.0...v0.18.1

v0.18.0

Compare Source

What's Changed

Full Changelog: v0.17.2...v0.18.0

v0.17.2

Compare Source

What's Changed

Full Changelog: v0.17.1...v0.17.2

v0.17.1

Compare Source

What's Changed

Full Changelog: v0.17.0...v0.17.1

v0.17.0

Compare Source

What's Changed

Full Changelog: v0.16.0...v0.17.0

v0.16.0

Compare Source

What's Changed

Full Changelog: v0.15.0...v0.16.0

v0.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: v0.14.1...v0.15.0

v0.14.1

Compare Source

What's Changed

Full Changelog: v0.14.0...v0.14.1


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@github-actions

Copy link
Copy Markdown

Dependency Bump Evaluation

Version change: github.com/scality/raidmgmt v0.14.0 -> v0.20.0 (6 minor versions)
Semver bump type: minor (multiple jumps)

Changes (v0.14.1 - v0.20.0):

  • v0.15.0: zerolog to log/slog migration, storcli2 adapter suite, IEC binary size units, command runners, controller/drive/volume getters, LV CRUD, physical drive blinker
  • v0.16.0: domain/core validation enrichment, e2e harness, CI release automation
  • v0.17.0: megaraid cache policy fix, SCSI bus rescan, IsPartition field on physical drives
  • v0.17.1-v0.17.2: megaraid SCSI rescan fix, ssacli empty controller fix
  • v0.18.0-v0.18.1: ssacli unassigned drive + LV creation fixes
  • v0.19.0: mockery v2 to v3 migration, storcli2/perccli2 NoIO policy, rhel8 lsblk JSON fix
  • v0.20.0: golang.org/x/mod v0.40.0 security fix, unhealthy drive inventory resilience

Breaking changes: None that affect this PR. The zerolog to slog migration (v0.15.0) and mockery v2 to v3 (v0.19.0) are significant API changes in the main module, but the scenario/go.mod has a replace github.com/scality/raidmgmt => ../ directive -- the version number is cosmetic, and the module always builds against the local source tree.

Security concerns: None introduced. v0.20.0 includes a security fix for golang.org/x/mod (transitive), which is already on main.

Impact on codebase: The scenario/ sub-module imports domain entities, implementation packages, and command runners from the main module. All resolved via the replace directive to the local checkout -- no published version is fetched. No zerolog usage exists in scenario/.

Recommendation: SAFE TO MERGE

Notes: CI checks (golangci-lint, tests) were still in progress at review time -- confirm they pass before merging. This is a self-referential dependency bump: the scenario/ sub-module pins a newer nominal version of its own parent repo, but the replace directive ensures the actual code is always the local tree. The effective change is limited to the version string in scenario/go.mod.

-- Claude Code

@scality-renovate
scality-renovate Bot force-pushed the renovate/github.com-scality-raidmgmt-0.x branch from 15a0b08 to 224d31a Compare October 26, 2026 08:21
@github-actions

Copy link
Copy Markdown

Dependency Bump Evaluation

Version change: v0.14.0 → v0.20.0 (6 minor bumps)
Semver bump type: minor (multi-version jump)

Changes (v0.14.0 → v0.20.0):

  • v0.14.1: tolerate predictive failure and unknown ssacli statuses
  • v0.15.0: zerolog → log/slog migration, storcli2 adapter suite, IEC binary size units
  • v0.16.0: enriched domain/core validation, e2e test harness
  • v0.17.0: IsPartition field on physical drives, cache policy fixes
  • v0.17.1–v0.17.2: SCSI bus rescan fix, ssacli empty controller fix
  • v0.18.0–v0.18.1: ssacli unassigned drive + logical volume creation fixes
  • v0.19.0: storcli2 NoIO policy, lsblk JSON parsing fix, mockery v2→v3 migration
  • v0.20.0: golang.org/x/mod security update, unhealthy drive inventory resilience

Breaking changes: None affecting the scenario module

Security concerns: None — v0.20.0 includes a golang.org/x/mod security fix, but the replace directive means the scenario module already uses whatever version the root module pins

Impact on codebase:

  • scenario/go.mod uses replace github.com/scality/raidmgmt => ../, so the version in go.mod is cosmetic — the dependency always resolves to the local checkout
  • The scenario module does not import zerolog (the breaking v0.15.0 migration is irrelevant)
  • The scenario module does not reference IsPartition or NoIOPolicy (new fields from later versions)
  • Only 1 file changed: scenario/go.mod (version string update)

Recommendation: SAFE TO MERGE

Notes: This is a low-risk change. The replace directive ensures the scenario module always compiles against the repo's current code regardless of the version string in go.mod. This bump simply aligns the declared minimum version with the latest release. CI checks were still in progress at time of review — confirm they pass before merging.

— Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants