docs(releases): Add release notes for v1.9.2

[yamadashy]

Add release notes for v1.9.2 documenting:

• Improved .gitignore handling with globby v16 (feat(core): Improve .gitignore handling with globby v16 #964)
• Fixed GitHub Actions compress option (fix (actions) remove no supported --no-compress argument #965)
• New contributor recognition for @chinchala

Checklist

• Run npm run test
• Run npm run lint

[coderabbitai]

Caution

Review failed

The pull request is closed.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

This PR adds v1.9.2 release documentation and a corresponding JSON schema file for Repomix configuration validation. The release notes describe .gitignore handling improvements, globby v16 dependency updates, and a GitHub Actions compress option bug fix. A new configuration schema file is introduced to validate the structure and values of repomix.config.json files.

Changes

Cohort / File(s)	Summary
Release Documentation \.github/releases/v1\.x/v1\.9\.2\.md	Release notes for v1.9.2 documenting .gitignore handling improvements with globby v16 update, GitHub Actions compress option bug fix, and contributor acknowledgments.
Configuration Schema website/client/src/public/schemas/1\.9\.2/schema\.json	New JSON Schema file defining Repomix configuration structure with validation rules for input, output, include, ignore, security, and tokenCount properties.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

• Schema file completeness: verify all configuration options are properly documented with correct types and constraints
• Release notes accuracy: confirm version number, feature descriptions, and attribution are correct

Possibly related PRs

• ci: update schema on main #778: Adds CI automation to generate and update published JSON schema files under website/client/src/public/schemas, which directly complements the manual schema file addition in this PR.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/release-notes-v1.9.2

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7e7baa2 and 9a4abde.

📒 Files selected for processing (2)

• .github/releases/v1.x/v1.9.2.md (1 hunks)
• website/client/src/public/schemas/1.9.2/schema.json (1 hunks)

---

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

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

[gemini-code-assist]

Summary of Changes

Hello @yamadashy, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the release notes for version v1.9.2, detailing significant improvements to .gitignore file processing for better Git compatibility and a crucial bug fix for the compress option within GitHub Actions workflows.

Highlights

• Improved .gitignore Handling: Updated to globby v16, enhancing .gitignore handling to match Git's standard behavior, including respecting parent directory .gitignore files for more intuitive and consistent file filtering.
• Fixed GitHub Actions compress Option: Corrected a bug where setting compress: false in GitHub Actions incorrectly added an unsupported --no-compress argument. The logic now ensures --compress is only added when explicitly enabled.
• New Contributor Recognition: Recognized @chinchala for their first contribution to the project.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[cloudflare-workers-and-pages]

Deploying repomix with    Cloudflare Pages

Latest commit:	9a4abde
Status:	✅  Deploy successful!
Preview URL:	https://8418e1fd.repomix.pages.dev
Branch Preview URL:	https://docs-release-notes-v1-9-2.repomix.pages.dev

View logs

[gemini-code-assist]

Code Review

This pull request adds the release notes for version 1.9.2. The notes are clear, well-structured, and accurately reflect the changes mentioned in the pull request description. I have one minor suggestion to improve conciseness by removing some redundant information in the description of an improvement.

[gemini-code-assist]

This paragraph repeats information that is also in the 'Key improvements' list below (e.g., 'Parent directory .gitignore files are now properly respected'). To make the notes more concise, I suggest simplifying this paragraph to a high-level summary and letting the list provide the specific details.

Suggested change

	Updated to globby v16 and enhanced `.gitignore` handling to match Git's standard behavior. Parent directory `.gitignore` files are now properly respected, making file filtering more intuitive and consistent with how Git itself operates.
	Updated to globby v16 to improve `.gitignore` handling, making file filtering more intuitive and consistent with Git's standard behavior.

[claude]

Code Review Summary

This PR adds release notes for v1.9.2 and the corresponding JSON schema. The documentation is well-written and follows the established format. Here's my review:

✅ Positive Aspects

1. Accurate Content: The release notes accurately reflect the changes in PRs feat(core): Improve .gitignore handling with globby v16 #964 and fix (actions) remove no supported --no-compress argument #965
2. Consistent Format: Follows the established pattern from previous releases (v1.9.1, v1.9.0)
3. Good Structure: Clear sections for Improvements and Bug Fixes with helpful emojis
4. Proper Attribution: Correctly credits @chinchala for their first contribution
5. Schema Consistency: The schema file is identical to v1.9.1, which is correct since no config changes were made

📝 Minor Observations

Version Discrepancy Note (Not a blocker)

PR #964 mentions in its body:

"While globby v16 introduced a breaking change in the gitignore option behavior, this change aligns Repomix with Git's standard behavior (respecting parent directory .gitignore files). This is why we're releasing this as a MINOR version (v1.10.0) rather than PATCH."

However, this PR is documenting it as v1.9.2 (patch version). This appears to be an intentional decision change, which is fine for this type of improvement. The release notes correctly describe it as an "Improvement" rather than a breaking change from the user's perspective.

Technical Accuracy

The description of the GitHub Actions fix is accurate:

• Correctly states that compress: false incorrectly added --no-compress
• Correctly states the fix ensures --compress is only added when explicitly enabled
• Verified against PR fix (actions) remove no supported --no-compress argument #965

The description of the globby upgrade is accurate:

• Correctly mentions globby v16 upgrade
• Accurately describes the behavior change (respecting parent directory .gitignore files)
• Verified against PR feat(core): Improve .gitignore handling with globby v16 #964

🎯 Recommendations

All recommendations are optional enhancements - the PR is ready to merge as-is:

1. Consider adding code examples: Previous release notes sometimes included before/after examples (like v1.9.1 for the file extension fix). This could help users understand the impact of the .gitignore changes.

2. Schema versioning: The schema is identical to v1.9.1. Consider whether future releases need schema changes or if we can continue using symbolic links/references to avoid duplication.

✨ Premortem Analysis

Potential issues and mitigations:

Scenario	Impact	Mitigation
Users expect v1.10.0 based on PR #964	Low - Version confusion	Release notes clearly document this as v1.9.2, no action needed
Schema file duplication	Low - Maintenance overhead	Future consideration: use symbolic links or references for unchanged schemas
Breaking behavior change not communicated	Medium - User surprise	Current notes are clear, but could add migration guidance if issues arise

🚀 Conclusion

Status: Ready to merge ✅

This is a solid documentation PR with no blocking issues. The release notes are clear, accurate, and follow project conventions. The minor observations above are informational only and don't require changes before merging.