chore(deps): update module github.com/pioz/faker to v2

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/pioz/faker	v1.7.3 → v2.7.2

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Updated internal dependencies for improved stability.

Walkthrough

The go.mod file was updated to replace the indirect YAML dependency from version 3 to version 2, changing gopkg.in/yaml.v3 v3.0.1 to gopkg.in/yaml.v2 v2.4.0 as a required module. No other module directives or exported entities were affected.

Changes

Cohort / File(s)	Summary
Dependency Version Update go.mod	Replaced YAML library indirect dependency from gopkg.in/yaml.v3 v3.0.1 to gopkg.in/yaml.v2 v2.4.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title claims to update github.com/pioz/faker to v2, but the actual changes only show gopkg.in/yaml dependency modifications with no pioz/faker changes.	Update the PR title to accurately reflect the actual changes made, such as 'chore(deps): update gopkg.in/yaml from v3 to v2' or clarify the pioz/faker update separately.
Description check	⚠️ Warning	The description details the update of github.com/pioz/faker from v1.7.3 to v2.7.2, but the raw_summary shows only gopkg.in/yaml dependency changes with no mention of pioz/faker modifications.	Ensure the description accurately matches the actual code changes shown in the raw_summary, or verify that the raw_summary is complete and includes all modified dependencies.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/master/github.com-pioz-faker-2.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@go.mod`:
- Line 69: The go.mod still references the old faker module version
"github.com/pioz/faker v1.7.3 // indirect" while the commit message claims a v2
upgrade; to fix, decide whether you truly intend to upgrade to v2 and if so
update imports and module path to "github.com/pioz/faker/v2" across the
codebase, run `go get github.com/pioz/faker/v2@latest` and `go mod tidy` to
update go.mod and go.sum, and then replace any remaining import lines
referencing "github.com/pioz/faker" to the new "/v2" path (or if you do not
intend to upgrade, adjust the commit message to remove the v2 claim); use the
module name "github.com/pioz/faker" and the new "github.com/pioz/faker/v2"
import to locate and update the code.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ab2fc58a-0f15-4700-a978-0a2b03095dce

📥 Commits

Reviewing files that changed from the base of the PR and between 2375ce5 and d39cd1f.

📒 Files selected for processing (1)

• go.mod

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# 1) Show faker entries in module files
rg -n -C2 'github.com/pioz/faker(/v2)?' go.mod go.sum || true

# 2) Show faker import paths in Go sources
rg -n -C2 '"github.com/pioz/faker(/v2)?"' --type go || true

# 3) Show YAML-related entries to confirm this PR's effective change
rg -n -C1 'gopkg.in/yaml.v2|gopkg.in/yaml.v3|go.yaml.in/yaml/v2' go.mod go.sum || true

Repository: RedHatInsights/widget-layout-backend

Length of output: 2893

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Check git log and commit messages for context
git log --oneline -5 2>/dev/null || echo "Git history unavailable"

# Check if there's a PR description or branch name that indicates intent
git branch -a 2>/dev/null | head -20 || true

# Look at the actual diff for go.mod to see what changed
git diff HEAD~1 go.mod 2>/dev/null || echo "No git diff available"

Repository: RedHatInsights/widget-layout-backend

Length of output: 268

---

Incomplete faker v2 upgrade: go.mod still pins v1.

The commit message indicates this should upgrade github.com/pioz/faker to v2, but go.mod line 50 still shows v1.7.3 // indirect, and no /v2 import paths were found in code. For a v2 major upgrade, Go requires module path migration to /v2. Either the upgrade is incomplete or the commit message is misleading.

The YAML dependency update (line 69) appears unrelated to this objective.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@go.mod` at line 69, The go.mod still references the old faker module version
"github.com/pioz/faker v1.7.3 // indirect" while the commit message claims a v2
upgrade; to fix, decide whether you truly intend to upgrade to v2 and if so
update imports and module path to "github.com/pioz/faker/v2" across the
codebase, run `go get github.com/pioz/faker/v2@latest` and `go mod tidy` to
update go.mod and go.sum, and then replace any remaining import lines
referencing "github.com/pioz/faker" to the new "/v2" path (or if you do not
intend to upgrade, adjust the commit message to remove the v2 claim); use the
module name "github.com/pioz/faker" and the new "github.com/pioz/faker/v2"
import to locate and update the code.