docs(changelog): Add initial changelog

[mertssmnoglu]

docs(changelog): Add initial changelog for version tracking and release notes

Summary by CodeRabbit

• Documentation
  • Introduced a changelog to track released versions, notable changes, and contributor acknowledgments for the project.

[coderabbitai]

Walkthrough

A new CHANGELOG.md file has been added to the project. This file provides a chronological record of released versions, including release dates, notable changes, commit references, and contributor acknowledgments. It covers the release history from version 1.0.0 to 1.0.1, detailing major features, improvements, and requirements. The changelog also outlines the release process, including date formatting and the use of cryptographic checksums for verification. No code or public API entities were altered in this update.

Changes

File(s)	Change Summary
CHANGELOG.md	Added a changelog documenting all released versions, key changes, commit references, and contributors.

Poem

In the garden of code, a log now appears,
Recording our progress through months and through years.
Each version a carrot, each fix a new leaf,
With hashes for safety and dates for relief.
So hop along, devs, and see what we've done—
Our changelog is growing, the journey’s begun!
🥕📜

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

CHANGELOG.md (3)

3-4: Improve introductory description clarity
Consider splitting the blockquote into shorter sentences and wrapping filenames or tools in backticks. For example:

> This `CHANGELOG.md` tracks all released versions and their changes.
> Releases are published via GitHub Actions and GoReleaser with cryptographic checksums for verification.

---

5-5: Standardize metadata key naming
For consistency with common markdown metadata, consider using:

Date format: YYYY-MM-DD

instead of Date-Format.

---

7-14: Clarify Checkmate upgrade instructions
The current note “If your version is higher than 2.0, you don't need to upgrade Checkmate.” may conflict with >= 2.0. To avoid confusion, you could revise to:

> Requires Checkmate >= 2.0  
> If you already have Checkmate v2.0 or above, no upgrade is needed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2e27788 and a513d6e.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

🔇 Additional comments (4)

CHANGELOG.md (4)

1-2: Header Format
The top‐level heading clearly identifies this as the changelog for the Capture project.

---

15-19: Release 1.0.1 entry looks good
The section header, release notes, commit links, and contributor acknowledgment are all clearly presented.

---

20-24: Release 1.0.0 header and description are clear
The initial release section correctly documents the version, date, and high‐level summary.

---

25-39: Commit references for 1.0.0 are comprehensive
All merged PRs and key commits are listed with descriptive links, making it easy to trace the history.