chore(main): release 0.1.0

[TFM-HITESH]

🤖 I have created a release beep boop

0.1.0 (2026-09-10)

Features

• add --json output to vaar diff (#60) (0c89a86)
• add dotenv key comparison engine (#53) (f4cf57b)
• add explicit lint target and target-dir scopes (e7a420a)
• add vaar diff command with text output (#55) (e8e12c5)
• allow JSON lint output to be written to a file (#19) (85b0253)
• launch the initial Vaar environment linter (be1f2cd)
• lint: add --list-rules for rule discovery (#30) (48441b2)
• lint: add constant-case rule (#33) (94d0988)
• lint: add value-without-quotes lint rule (#44) (2b5383d)
• lint: give rules a fix half; derive fixability and the FIXABLE column from it (#45) (725110a), closes #40

Bug Fixes

• discover arbitrary dotenv filenames (#56) (6a28936)
• discover dotenv files under examples directories (fabd3ff)
• lint: confirm successful --output writes on stderr (#29) (54c09e9), closes #22
• lint: harden --output write path against directory and temp-dir bugs (#37) (71cd174)
• lint: reject --output that would overwrite a lint input (#28) (0bbc249)
• lint: scope --fix to the selected rules via per-rule fixes (#54) (e34569f)
• report repaired findings with --fix (#18) (9f9b97c)

Performance Improvements

• lint: skip second lint pass when --fix changes no files (#24) (#25) (6e91f38)
• lint: skip the second pass when no fixes were applied (#32) (0d2a841), closes #25 #24

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The release manifest records root version 0.1.0, and CHANGELOG.md adds the dated release section with feature, bug-fix, and performance entries while reorganizing its header block.

Changes

Release metadata

Layer / File(s)	Summary
Release manifest and changelog .release-please-manifest.json, CHANGELOG.md	The root package version is set to 0.1.0, and the changelog records the 0.1.0 (2026-07-16) release with Features, Bug Fixes, and Performance Improvements sections and updated header placement.

Estimated code review effort: 1 (Trivial) | ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	The diff only shows release metadata, so the implementation and tests for #22 cannot be verified from this PR.	Provide the code changes or release-linked commit diff showing the stderr confirmation, exit-code behavior, and tests for #22.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Out of Scope Changes check	✅ Passed	The manifest and changelog updates are expected for a release PR and do not appear unrelated.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the release of version 0.1.0, which matches the main changes in the manifest and changelog.

---

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.}

[coderabbitai]

🧹 Nitpick comments (1)

CHANGELOG.md (1)

1-21: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Keep the changelog header and metadata in one consistent block.

The file now has both # Changelog and a later ## Changelog, while the copyright/SPDX and explanatory text appear after the 0.1.0 release notes. Keep a single heading and place the static metadata before versioned sections so generated releases remain easy to navigate.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 1 - 21, Update the CHANGELOG structure to retain a
single Changelog heading, move the copyright/SPDX metadata immediately beneath
that header and before the 0.1.0 release section, and remove the duplicate
trailing heading and metadata block while preserving the release notes.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CHANGELOG.md`:
- Around line 1-21: Update the CHANGELOG structure to retain a single Changelog
heading, move the copyright/SPDX metadata immediately beneath that header and
before the 0.1.0 release section, and remove the duplicate trailing heading and
metadata block while preserving the release notes.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8b0e4d53-fdc7-444f-92de-2d88d94a7ab0

📥 Commits

Reviewing files that changed from the base of the PR and between 9f9b97c and 8965936.

📒 Files selected for processing (2)

• .release-please-manifest.json
• CHANGELOG.md