chore(main): release 1.3.0

[pushpak1300]

🤖 I have created a release beep boop

1.3.0 (2024-10-22)

Features

• add retry ability on email assertion commands(#40) (93a04da), closes #39

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Introduced retry capability on email assertion commands.

• Chores

  • Updated version number to 1.3.0 in relevant files.
  • Updated CHANGELOG to document new features and changes.

[coderabbitai]

Walkthrough

The pull request updates the version number across multiple files, changing it from 1.2.1 to 1.3.0. It also adds a new entry in the changelog detailing the new feature that introduces retry capability on email assertion commands, which addresses issues #39 and #40. The structure of the changelog remains consistent with previous entries, documenting the changes made in this release.

Changes

File	Change Summary
.release-please-manifest.json	Version updated from 1.2.1 to 1.3.0.
CHANGELOG.md	New version entry for 1.3.0 added; feature for retry ability on email assertion commands documented.
package.json	Version updated from 1.2.1 to 1.3.0.

Assessment against linked issues

Objective	Addressed	Explanation
Automatic waiting and retries for queries (#39)	✅

Possibly related PRs

• chore(main): release 1.2.1 #36: The changes in this PR involve updating the version number in the .release-please-manifest.json and package.json files, similar to the version update from 1.2.1 to 1.3.0 in the main PR.
• chore(main): release 1.2.0 #34: This PR also updates the version number in the .release-please-manifest.json and package.json, reflecting a previous version increment, indicating a consistent versioning approach across releases.

Suggested labels

autorelease: tagged, enhancement

Poem

In the garden of code, we hop and play,
With version updates brightening the way.
Retry commands now dance with glee,
As bugs retreat, oh so happily!
Hooray for the changes, let’s cheer and shout,
For in this release, we’ve figured it out! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3037914 and b4c835e.

⛔ 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 context used

🔇 Additional comments (2)

CHANGELOG.md (2)

5-6: LGTM: Version entry follows standard format.

The version entry is properly formatted with the correct GitHub comparison link and follows the established date format.

---

8-10: LGTM: Feature entry is well-documented.

The feature entry properly documents the new retry ability on email assertion commands and correctly references the related issues (#39, #40).

Let's verify the issue references:

✅ Verification successful

Changelog entry correctly references related issues and implementation

The verification confirms that both referenced issues (#39 and #40) are properly linked and directly related to the retry functionality:

• Issue Feature Request: automatic waiting and retries for queries #39 is a feature request for "automatic waiting and retries for queries"
• Issue feat(refactor): improve email search commands #40 contains the implementation details mentioning the waitForCondition method for retry logic

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the referenced issues exist and are properly linked
# Expected: Both issues should exist and be related to retry functionality

# Test: Check if issues #39 and #40 exist and contain relevant keywords
gh issue view 39 --json title,body | jq -r '.title, .body' | grep -i "retry\|wait"
gh issue view 40 --json title,body | jq -r '.title, .body' | grep -i "retry\|wait"

Length of output: 622

---

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>, please review it.
  • 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 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 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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

[pushpak1300]

🤖 Created releases:

• v1.3.0
  🌻