Add 1.0.4 release entry to CHANGELOG

[koriym]

Summary

• Add the 1.0.4 entry to CHANGELOG.md covering the DbPager Pager mutation fix merged in Clone Pager attribute in DbPager::__invoke to prevent mutation #81 / closes DbPager mutates the #[Pager] attribute instance it receives #80.

Test plan

• CHANGELOG format matches the existing 1.0.3 entry

Summary by Sourcery

Documentation:

• Add a 1.0.4 changelog entry describing the DbPager pager mutation bug fix.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Documents the 1.0.4 release in CHANGELOG.md, describing the DbPager Pager-mutation bug fix and aligning the new entry with the existing changelog format.

File-Level Changes

Change	Details	Files
Add a 1.0.4 release section to the changelog for the DbPager Pager-mutation bug fix.	Introduce a new 1.0.4 heading with release date following Keep a Changelog format Add a Fixed subsection describing that DbPager::__invoke() now clones the Pager attribute instance to avoid mutating the caller's Pager Reference related GitHub issue DbPager mutates the #[Pager] attribute instance it receives #80 and pull request Clone Pager attribute in DbPager::__invoke to prevent mutation #81 in the changelog entry	CHANGELOG.md

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#80	Modify DbPager::__invoke so that it no longer mutates the Pager instance it receives (e.g., by cloning the Pager at the top of the method), ensuring perPage is not overwritten on the caller's attribute instance.	❌	The PR only adds a 1.0.4 entry to CHANGELOG.md describing that the DbPager Pager mutation bug was fixed in a previous PR (#81). It does not change DbPager::__invoke or any runtime code, so it does not itself implement the behavioral fix requested in the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@koriym has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 43 minutes and 0 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 43 minutes and 0 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 98963a93-f253-4904-b306-c16438535fcf

📥 Commits

Reviewing files that changed from the base of the PR and between c5c25ab and 7fc0485.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-1.0.4

---

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

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}