Use right tag

[joselsegura]

Description

Please, be the last one.

The referenced workflow from the caller is an old version not having the secrets definition

Type of change

• Configuration update

Testing steps

Another one in CI

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e6ed2dac-8a0d-4e36-ae85-7b4a9a8333fa

📥 Commits

Reviewing files that changed from the base of the PR and between 28fd8be and 55df322.

📒 Files selected for processing (3)

• workflows_examples/bdd.yaml
• workflows_examples/bots-auto-merge.yaml
• workflows_examples/linters.yaml

---

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow versions to latest compatible releases for improved build and testing reliability.

Walkthrough

Three workflow files in workflows_examples/ updated to reference reusable workflow versions v0.3.1 instead of v0.2.0 from RedHatInsights/processing-tools. Job inputs and configurations remain unchanged.

Changes

Cohort / File(s)	Summary
Reusable workflow version updates workflows_examples/bdd.yaml, workflows_examples/bots-auto-merge.yaml, workflows_examples/linters.yaml	Reusable workflow references bumped from v0.2.0 to v0.3.1 across three workflow files. All job inputs and configurations unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Use right tag' is vague and non-descriptive, failing to convey what specific tag is being updated or why.	Use a more descriptive title that specifies the workflow versions being updated, such as 'Update reusable workflows to v0.3.1' or 'Upgrade processing-tools workflows from v0.2.0 to v0.3.1'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description relates to the changeset by explaining that outdated workflow versions lacking secrets definitions are being updated, which matches the PR's intent.
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

---

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