chore: upgrade sdk version

[aimensahnoun]

Summary by CodeRabbit

• Chores
  • Updated the package version from 0.3.0 to 0.3.1.
  • Updated the dependency on @requestnetwork/request-client.js to version ^0.49.1-next.2088.

[coderabbitai]

Walkthrough

The pull request updates the package.json file for the @requestnetwork/payment-widget package. The version number has been incremented from 0.3.0 to 0.3.1, and the dependency on @requestnetwork/request-client.js has been modified from version ^0.49.0 to ^0.49.1-next.2088. No other fields in the package.json have been changed, maintaining the overall structure and configuration of the package.

Changes

File	Change Summary
packages/payment-widget/package.json	- Version updated from 0.3.0 to 0.3.1
	- Dependency updated from ^0.49.0 to ^0.49.1-next.2088

Possibly related PRs

• chore: increase package size for release #125: This PR also updates the version number in the package.json file for the @requestnetwork/payment-widget package, indicating a similar type of change related to version management.
• chore: increase payment-widget version #145: This PR updates the version number in the package.json file for the @requestnetwork/payment-widget package, which is directly related to the changes made in the main PR regarding version updates.

Suggested reviewers

• MantisClone
• sstefdev
• rodrigopavezi

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ccfa0fb and 257825a.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• packages/payment-widget/package.json (2 hunks)

🔇 Additional comments (2)

packages/payment-widget/package.json (2)

3-3: Version bump looks appropriate.

The minor version increment (0.3.0 -> 0.3.1) follows semantic versioning for backward-compatible changes.

Let's verify version alignment with related packages:

---

60-60: ⚠️ Potential issue

Caution: Using pre-release dependency in production code.

The dependency @requestnetwork/request-client.js is being updated to a pre-release version ^0.49.1-next.2088. Using pre-release versions in production code can introduce instability:

• Pre-release versions may contain breaking changes
• They might not have gone through complete testing
• Could introduce unexpected behavior in the payment widget

Consider:

1. Using the latest stable version instead
2. If the pre-release version is necessary, document why it's needed
3. Add integration tests to verify the widget's functionality with this version

Let's check the available versions and recent changes:

✅ Verification successful

Using Pre-release Dependency Is Justified but Requires Caution

The dependency @requestnetwork/request-client.js is set to a pre-release version ^0.49.1-next.2088 as there are no stable releases beyond 0.49.0. Ensure you:

• Document the necessity for using the pre-release.
• Implement comprehensive integration tests to verify functionality.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check available versions and recent changes for request-client.js

# Get latest stable and pre-release versions from npm
echo "Available versions:"
npm view @requestnetwork/request-client.js versions --json

# Check for recent releases and their dates
echo -e "\nRelease timeline:"
npm view @requestnetwork/request-client.js time --json

Length of output: 51760

---

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.