Skip to content

chore: switch to @tony.ganchev/eslint-plugin-header#641

Open
tonyganchev wants to merge 1 commit intoar-io:developfrom
tonyganchev:develop
Open

chore: switch to @tony.ganchev/eslint-plugin-header#641
tonyganchev wants to merge 1 commit intoar-io:developfrom
tonyganchev:develop

Conversation

@tonyganchev
Copy link
Copy Markdown

This fork of eslint-plugin-header supports ESLint 9 without any hacks necessary to bypass schema validation.

Furthermore it is continuously updated,, has many bug-fixes, particularly for Windows support, and comes with significant UX improvements such as more precise violation messages, line reports. etc.

Notes:

  • The header configuration enforces 2025 as the two-year. I assume eventually the whole codebase will need to be updated for 2026. Instead, using regex matching, years can be configured to match a format - and still support autofix.
  • based on the above, if a single-line regex is used, you don't need to disable linting of src/lib/bundles.ts

This fork of eslint-plugin-header supports ESLint 9 without any hacks necessary to bypass schema validation.

Furthermore it is continuously updated,, has many bug-fixes, particularly for Windows support, and comes with significant UX improvements such as more precise violation messages, line reports. etc.

Notes:
- The header configuration enforces 2025 as the two-year. I assume eventually the whole codebase will need to be updated for 2026. Instead, using regex matching, years can be configured to match a format - and still support autofix.
- based on the above, if a single-line regex is used, you don't need to disable linting of src/lib/bundles.ts
@tonyganchev tonyganchev changed the title chore: @tony.ganchev/eslint-plugin-header chore: switch to @tony.ganchev/eslint-plugin-header Mar 14, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 14, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 3c3c86bb-2709-43e3-bcd1-09bcdfc63ca0

📥 Commits

Reviewing files that changed from the base of the PR and between 611b5cf and 5ba92b6.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • eslint.config.mjs
  • package.json

📝 Walkthrough

Walkthrough

The pull request updates the ESLint header plugin dependency from the unscoped eslint-plugin-header package to the scoped variant @tony.ganchev/eslint-plugin-header (v3.3.0). The configuration is updated to use the new import, and a schema workaround is removed.

Changes

Cohort / File(s) Summary
Header Plugin Dependency Update
eslint.config.mjs, package.json
Replaced eslint-plugin-header dependency with scoped package @tony.ganchev/eslint-plugin-header (^3.3.0) in manifest and configuration. Removed schema workaround in ESLint config, suggesting the scoped package resolves the original issue.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: switching from eslint-plugin-header to @tony.ganchev/eslint-plugin-header, which is directly reflected in the file changes.
Description check ✅ Passed The description is directly related to the changeset, explaining the rationale for switching to the fork, its benefits (ESLint 9 support, bug fixes), and implementation notes about header configuration.
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
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

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

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

Tip

You can customize the tone of the review comments and chat replies.

Configure the tone_instructions setting to customize the tone of the review comments and chat replies. For example, you can set the tone to Act like a strict teacher, Act like a pirate and more.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant