Prepare release v1.9.1

[juanhiginio]

Prepare release v1.9.1

Summary by CodeRabbit

• Chores
  • Updated the changelog to include details for version 1.9.1.
  • Bumped the application version to 1.9.1.

[coderabbitai]

Walkthrough

The changes update the project version from 1.9.0 to 1.9.1 in the version file and add a corresponding entry for version 1.9.1 in the changelog, documenting a client refactor and referencing pull request #149.

Changes

Files	Change Summary
CHANGELOG.md	Added entry for version 1.9.1 with refactor note and PR ref
lib/bas/version.rb	Updated VERSION constant from "1.9.0" to "1.9.1"

Possibly related PRs

• Prepare release v1.9.0 #148: Updates version from 1.8.1 to 1.9.0 and adds a changelog entry, similar in scope for the previous release.
• Prepare release v1.7.2 #141: Updates version from 1.7.1 to 1.7.2 and adds a changelog entry, involving the same files for another version bump.

Suggested reviewers

• L-Zuluaga

Poem

A hop to one-nine-one, so spry,
The changelog’s fresh, the numbers fly!
With versions bumped and notes anew,
The client’s ready for what’s in view.
🐇✨
Another leap, another cheer—
The code hops on to a brand new year!

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.

[coveralls]

Pull Request Test Coverage Report for Build 16306973351

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 98.153%

---

Totals
Change from base Build 16306900263:	0.0%
Covered Lines:	1701
Relevant Lines:	1733

---

💛 - Coveralls

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

3-5: Verify release date & wording

1. Both 1.9.1 and 1.9.0 entries show 15.07.2025. If 1.9.1 is being cut later, update the date to the actual release day to avoid ambiguity.
2. The bullet reads “Refactor client to meet the needs of the implementation to be performed” — the tail phrase is vague. Consider tightening it to something like “…for upcoming implementation requirements”.

-# 1.9.1 (15.07.2025)
- - [refactor: Refactor client to meet the needs of the implementation to be performed](https://github.com/kommitters/bas/pull/149)
+# 1.9.1 (DD.MM.YYYY)
+- [refactor: Align client with upcoming implementation requirements](https://github.com/kommitters/bas/pull/149)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 48f991b and abafcdb.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• lib/bas/version.rb (1 hunks)

🔇 Additional comments (1)

lib/bas/version.rb (1)

5-5: Keep the gemspec in sync with the new version constant

VERSION is now "1.9.1". Double-check that the gemspec (and any CI release scripts) have been bumped to the same value; otherwise gem build / gem push will still publish 1.9.0.