Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(master): release 1.3.1 #267

Conversation

lotyp
Copy link
Member

@lotyp lotyp commented May 18, 2024

🤖 I have created a release beep boop

1.3.1 (2024-05-21)

Documentation


This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Chores
    • Updated internal version from "1.3.0" to "1.3.1" for release management.

Copy link

coderabbitai bot commented May 18, 2024

Walkthrough

The recent update involves a minor version bump in the release manifest from 1.3.0 to 1.3.1. No significant changes were observed in other files.

Changes

File Change Summary
.github/.../.release-please-manifest.json Updated version to "1.3.1"
CHANGELOG.md No significant changes found

🐇✨ In the land of code, where versions grow,
A tiny bump, a gentle flow.
From 1.3.0 to 1.3.1,
No public shifts, the work is done.
A rabbit hops with joy and cheer,
For stable paths are always dear. 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link

codecov bot commented May 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.41%. Comparing base (9e5b58d) to head (f44af18).

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #267   +/-   ##
=========================================
  Coverage     55.41%   55.41%           
  Complexity       18       18           
=========================================
  Files             3        3           
  Lines           240      240           
=========================================
  Hits            133      133           
  Misses          107      107           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@lotyp lotyp force-pushed the release-please--branches--master--components--php-cs-fixer-config branch 2 times, most recently from 6878e9d to 6ccf8b0 Compare May 18, 2024 16:48
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 09f675f and bc2bb6a.
Files selected for processing (2)
  • .github/.release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
Files skipped from review due to trivial changes (1)
  • .github/.release-please-manifest.json
Additional Context Used
LanguageTool (1)
CHANGELOG.md (1)

Near line 611: Did you mean “running”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...0ee3c0c45b1c)) ### Bug Fixes * allow to run on php 8.2 ([8c86113](https://github.co...

Additional comments not posted (1)
CHANGELOG.md (1)

3-10: The changelog entries for version 1.3.1 correctly reference the commits associated with the README updates. This aligns with the PR's objective to update documentation for the new release.

@lotyp lotyp force-pushed the release-please--branches--master--components--php-cs-fixer-config branch from bc2bb6a to f44af18 Compare May 21, 2024 09:32
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between bc2bb6a and f44af18.
Files selected for processing (2)
  • .github/.release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • .github/.release-please-manifest.json
Additional Context Used
LanguageTool (1)
CHANGELOG.md (1)

Near line 612: Did you mean “running”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...0ee3c0c45b1c)) ### Bug Fixes * allow to run on php 8.2 ([8c86113](https://github.co...

Additional comments not posted (1)
CHANGELOG.md (1)

3-11: The changelog entries for version 1.3.1 correctly reference the commits related to README updates. This aligns with the PR's objective of updating documentation. Good job maintaining clarity and consistency in documenting these changes.

@lotyp lotyp disabled auto-merge May 23, 2024 10:33
@lotyp lotyp merged commit 745b27b into master May 23, 2024
24 checks passed
@lotyp lotyp deleted the release-please--branches--master--components--php-cs-fixer-config branch May 23, 2024 10:33
@lotyp
Copy link
Member Author

lotyp commented May 23, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant