chore: rename attribute

[gberenice]

what

• matchfilenames should fix this issue:

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: .github/renovate.json5
Error type: The renovate configuration file contains some invalid settings
Message: Invalid regExp for terraform.fileMatch: **/*.tf, Invalid regExp for terraform.fileMatch: **/*.tofu

why

• I break things.

references

• Action Required: Fix Renovate Configuration #19

Summary by CodeRabbit

• Chores
  • Updated configuration for dependency management; no impact on end-user experience.

[Gowiem]

[coderabbitai]

Walkthrough

This change updates the .github/renovate.json5 configuration file by renaming the key "matchFiles" to "matchFileNames" within three separate rules under the packageRules section. These rules are responsible for specifying file-matching patterns that target files with .tofu and .tf extensions. The update affects only the key name used to define file matching criteria; all other logic, values, and rule structures remain unchanged. No changes were made to any exported or public entities.

Possibly related PRs

• feat(renovate): enables renovate terraform manager #18: Introduces the initial .github/renovate.json5 configuration file, establishing the Renovate setup and targeting Terraform files, which relates directly to the current PR's update of key names within the same configuration file.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 89dfac7 and 3af6663.

📒 Files selected for processing (1)

• .github/renovate.json5 (1 hunks)

🔇 Additional comments (4)

.github/renovate.json5 (4)

41-41: Key rename looks good.

The change from matchFiles to matchFileNames is correct according to Renovate documentation. This will properly target both .tofu and .tf files using the glob patterns.

---

46-46: Key rename is consistent.

The change from matchFiles to matchFileNames for OpenTofu files is correct and consistent with the Renovate configuration schema.

---

51-51: Key rename is appropriate.

The change from matchFiles to matchFileNames for Terraform files is correct and properly completes the fix for all relevant rules.

---

41-53:

❓ Verification inconclusive

Verification of the fix.

These changes align with the PR objectives to fix the invalid regex patterns causing Renovate to stop working. The matchFileNames key properly handles glob patterns like **/*.tf and **/*.tofu which were previously being incorrectly interpreted as regular expressions.

---

🏁 Script executed:

#!/bin/bash
# Validate the renovate.json5 configuration format
npx --yes renovate-config-validator .github/renovate.json5

Length of output: 495

---

Manual Verification Required: Renovate Config Validator Not Found

The npx renovate-config-validator .github/renovate.json5 step failed because there’s no published renovate-config-validator package. To ensure your JSON5 syntax and Renovate settings are valid, please verify manually:

• Install and run the official Renovate config validator

npm install --save-dev @renovate/config-validator
npx renovate-config-validator .github/renovate.json5

• Or, at minimum, check JSON5 syntax with:

npm install --yes json5
npx json5 .github/renovate.json5

• Optionally, run Renovate in dry-run mode or paste your config into the Renovate Playground to confirm it loads without errors.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.