chore(main): release 4.0.0

[udondan]

🤖 I have created a release beep boop

4.0.0 (2024-04-10)

⚠ BREAKING CHANGES

• renames lambda property to lambdaFunction (#100)

Features

• adds option to define LogLevel for debugging lambda problems (#106) (0b7db4d)

Bug Fixes

• fix renovate building, cannot work with local packages (#113) (e26750b)
• upgrade lambda version to node 20 (#79) (cc5d917)

Miscellaneous Chores

• renames lambda property to lambdaFunction (#100) (881c7c0)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Rate Limit Exceeded

@udondan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 33 seconds before requesting another review.

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.

Commits

Files that changed from the base of the PR and between 27d0eb0 and e95f4d6.

Walkthrough

The recent update marks a significant transition from version 3.0.0 to 4.0.0, showcasing a pivotal evolution in the project. This version leap introduces an essential bug fix that enhances the lambda function by upgrading its runtime to Node.js 20 and renaming the lambda property to lambdaFunction, ensuring a smoother and more efficient operation.

Changes

File(s)	Change Summary
.release-please-manifest.json, package.json	Updated version number from "3.0.0" to "4.0.0".
CHANGELOG.md	Added a bug fix note for version 4.0.0: upgraded lambda to Node 20 and renamed lambda to lambdaFunction.

---

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

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

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 47b7bbd and 8000c84.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• .release-please-manifest.json (1 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

Files skipped from review due to trivial changes (2)

• .release-please-manifest.json
• package.json

Additional comments not posted (1)

CHANGELOG.md (1)

3-8: The changelog update for version 3.0.1 is clear and accurately documents the bug fix related to upgrading the lambda version to Node 20. The links to the issue and the commit provide excellent traceability. Well done!

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between d05a223 and 4e1aa29.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• .release-please-manifest.json (1 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• .release-please-manifest.json
• package.json

Additional comments not posted (1)

CHANGELOG.md (1)

3-8: The update to the changelog for version 3.0.1, detailing the upgrade of the lambda version to Node 20, is clear and accurately references the relevant issue and commit. This provides a concise and informative summary of the changes made in this release.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 76efbae and e1697f3.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• .release-please-manifest.json (1 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• .release-please-manifest.json
• package.json

Additional comments not posted (1)

CHANGELOG.md (1)

1-8: The changes in the CHANGELOG.md file accurately document the bug fix in version 3.0.1, including the upgrade of the lambda version to Node 20. The formatting follows conventional standards, and the links to the issue and commit are correctly included. Great job maintaining clarity and precision in the changelog.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 7a8acbb and ac096a8.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• .release-please-manifest.json (1 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• .release-please-manifest.json
• package.json

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 67f5809 and d04bdc7.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• .release-please-manifest.json (1 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• .release-please-manifest.json
• package.json

Additional comments not posted (3)

CHANGELOG.md (3)

6-8: The breaking change is well-documented, clearly indicating the renaming of the lambda property to lambdaFunction.

---

10-12: The bug fix regarding the upgrade of the lambda version to Node 20 is accurately documented.

---

15-17: The repetition of the breaking change under "Miscellaneous Chores" is noted. Please confirm if this is intentional to highlight its importance.

[coderabbitai]

Actionable comments posted: 1