Skip to content

chore(master): release 3.1.0 #64

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

Merged

Conversation

lotyp
Copy link
Member

@lotyp lotyp commented Apr 19, 2024

🤖 I have created a release beep boop

3.1.0 (2024-05-09)

Features

  • use markdown-linter in CI and locally (f0830f0)

Documentation


This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Updated app version to 3.1.0.
    • Improved documentation with updated badges and logo in the README.
  • Chores

    • Updated version information in the manifest and package files.

Copy link

coderabbitai bot commented Apr 19, 2024

Walkthrough

The recent project update brings version 3.1.0, featuring a markdown linter for enhanced code quality. Notable changes include a revamped README with updated badges and a fresh logo.

Changes

Files Change Summary
.github/.release-please-manifest.json, package.json Updated version from "3.0.0" to "3.1.0"
CHANGELOG.md Added markdown-linter, badge updates, and README modifications

🐰✨
In the realm of code and byte,
A rabbit dances with delight.
New version, linting in flight,
Logo gleams, badges bright!
Onward it hops, in the coding night. 🌟
🐰💻


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.

@lotyp lotyp force-pushed the release-please--branches--master--components--gh-actions branch 2 times, most recently from e380044 to 56c8c50 Compare April 22, 2024 00:11
@lotyp lotyp changed the title chore(master): release 3.0.1 chore(master): release 3.1.0 Apr 24, 2024
@lotyp lotyp force-pushed the release-please--branches--master--components--gh-actions branch 7 times, most recently from b301ecb to a00dc0e Compare April 26, 2024 15:50
@lotyp lotyp force-pushed the release-please--branches--master--components--gh-actions branch from a00dc0e to dfeaf7b Compare May 9, 2024 12:58
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: 2

Out of diff range and nitpick comments (1)
CHANGELOG.md (1)

Line range hint 52-52: Please reduce multiple consecutive blank lines to a single blank line for better readability and consistency.

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

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

Near line 3: Unpaired symbol: ‘[’ seems to be missing
Context: # Changelog ## [3.1.0](https://github.com/wayofdev/gh-actions/...


Near line 22: Unpaired symbol: ‘[’ seems to be missing
Context: ...ebd5b263af4b315956166f7af2d)) ## [3.0.0](https://github.com/wayofdev/gh-actions/...


Near line 50: Unpaired symbol: ‘[’ seems to be missing
Context: ...f3aca34555ff19f01bee9367b18)) ## [2.0.0](https://github.com/wayofdev/gh-actions/...


Near line 72: Did you mean “passing”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...d82bd55f5db50682b4d121f4b6393)) * allow to pass custom head reference ([3fddee2](https:...


Near line 73: Did you mean “passing”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun.
Context: ...76edb19d9c0a1e6e460446f345484)) * allow to pass platform in docker-build ([38174a4](htt...


Near line 74: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “below” or “further on” (in a document).
Context: ...a409e8d5bb48c4cac41daa0033a08e36989)) * infra files, fixes in actions ([22fb724](http...


Near line 99: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...e github_token within workflow_call can not be used since it would collide with sys...

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

3-3: Ensure that the markdown link is correctly formatted. It seems there might be an unpaired '[' symbol.


21-21: Ensure that the markdown link is correctly formatted. It seems there might be an unpaired '[' symbol.


Line range hint 50-50: Ensure that the markdown link is correctly formatted. It seems there might be an unpaired '[' symbol.

Comment on lines +5 to +10

### Features

* use markdown-linter in CI and locally ([f0830f0](https://github.com/wayofdev/gh-actions/commit/f0830f06b6cb7f3fdbeda015e808f9a094b2f09d))


Copy link

Choose a reason for hiding this comment

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

Please reduce multiple consecutive blank lines to a single blank line for better readability and consistency.


Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
### Features
* use markdown-linter in CI and locally ([f0830f0](https://github.com/wayofdev/gh-actions/commit/f0830f06b6cb7f3fdbeda015e808f9a094b2f09d))
### Features
* use markdown-linter in CI and locally ([f0830f0](https://github.com/wayofdev/gh-actions/commit/f0830f06b6cb7f3fdbeda015e808f9a094b2f09d))

* update readme logo ([75e4b9a](https://github.com/wayofdev/gh-actions/commit/75e4b9abe96364f2835d37522b9e7606bd18b9fa))
* updating readme ([bc5ff9c](https://github.com/wayofdev/gh-actions/commit/bc5ff9cb410a5ef64a99884c0db216dc7b7053eb))
* updating twitter badge ([88f5cac](https://github.com/wayofdev/gh-actions/commit/88f5cacc2a31cebd5b263af4b315956166f7af2d))

## [3.0.0](https://github.com/wayofdev/gh-actions/compare/v2.0.0...v3.0.0) (2024-04-18)


Copy link

Choose a reason for hiding this comment

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

Please reduce multiple consecutive blank lines to a single blank line for better readability and consistency.


Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

@lotyp lotyp merged commit daa0b76 into master May 11, 2024
@lotyp lotyp deleted the release-please--branches--master--components--gh-actions branch May 11, 2024 20:42
@lotyp
Copy link
Member Author

lotyp commented May 11, 2024

🤖 Release is at https://github.com/wayofdev/gh-actions/releases/tag/v3.1.0 🌻

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