chore: bumnp dma-library

[halaprix]

Title

Changes 👷‍♀️

- item 1

How to test 🧪

- step 1 ...

Summary by CodeRabbit

• Chores
  • Updated the version of the @oasisdex/dma-library dependency to enhance functionality and potentially address bugs.

[coderabbitai]

Walkthrough

The pull request modifies the package.json file for the oasis-borrow project by updating the version of the @oasisdex/dma-library dependency from 0.6.78 to 0.6.79. This change indicates an increment in the library's version, likely reflecting updates in functionality or bug fixes. No other modifications to dependencies, scripts, or configurations were made.

Changes

File	Change Summary
package.json	Updated @oasisdex/dma-library version from 0.6.78 to 0.6.79

Possibly related PRs

• chore: handle new morpho token and wrapper #4050: The main PR updates the version of the @oasisdex/dma-library dependency, while this retrieved PR also updates the @oasisdex/addresses dependency, indicating a related context of dependency management within the same project.

Poem

In the garden of code, where the libraries bloom,
A version was changed, dispelling the gloom.
From 0.6.78 to 0.6.79,
New features await, oh how they shine!
With hops and with skips, our project takes flight,
A leap toward the future, all coded just right! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2381388 and 0dfa2df.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (2)

package.json (2)

48-48: LGTM, but please verify the changelog

The version bump from 0.6.78 to 0.6.79 looks good. As this is a patch version update, it should only contain backward-compatible bug fixes.

Let's verify the changelog and release notes for this version:

---

48-48: Verify compatibility with other @OasisDEX packages

Since this project uses multiple @OasisDEX packages, ensure that this version of dma-library is compatible with:

• @oasisdex/[email protected]
• @oasisdex/[email protected]
• @oasisdex/multiply@^0.2.11
• @oasisdex/[email protected]
• @oasisdex/utils@^0.0.8

Let's check for any peer dependency requirements:

✅ Verification successful

Dependencies are compatible based on shared dependencies and version resolution

Based on the yarn.lock analysis:

• All @OasisDEX packages are successfully resolved without conflicts
• Common dependencies like bignumber.js and ethers are compatible:
  • dma-library uses ethers ^5.7.2
  • automation uses ethers ^5.6.2
  • All packages using bignumber.js use version 9.x

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check peer dependencies and cross-package compatibility

# Check package.json of dma-library v0.6.79 for peer dependencies
curl -s https://registry.npmjs.org/@oasisdex/dma-library/0.6.79 | jq '.peerDependencies'

# Search for imports of dma-library in the codebase to verify usage patterns
rg --type ts --type tsx '@oasisdex/dma-library'

Length of output: 169

---

Script:

#!/bin/bash
# Let's try a different approach to check compatibility

# 1. Check the current package versions in package.json
echo "Current package versions:"
cat package.json | jq '.dependencies | with_entries(select(.key | startswith("@oasisdex")))'

# 2. Search for imports using ripgrep with correct file extensions
echo -e "\nImport patterns:"
rg -t ts -t typescript -t js -t jsx "@oasisdex/dma-library"

# 3. Check if there's a yarn.lock or package-lock.json to analyze resolved versions
echo -e "\nLock file analysis:"
if [ -f yarn.lock ]; then
    echo "Found yarn.lock:"
    grep -A 5 "@oasisdex/" yarn.lock
elif [ -f package-lock.json ]; then
    echo "Found package-lock.json:"
    cat package-lock.json | jq '.dependencies | with_entries(select(.key | startswith("@oasisdex")))'
fi

Length of output: 2798

---

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.