Skip to content
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

build: 1.0.0-rc.5 #1568

Merged
merged 1 commit into from
Dec 10, 2024
Merged

build: 1.0.0-rc.5 #1568

merged 1 commit into from
Dec 10, 2024

Conversation

lucanicoladebiasi
Copy link
Collaborator

@lucanicoladebiasi lucanicoladebiasi commented Dec 10, 2024

Description

1.0.0-rc.5 build.

Summary by CodeRabbit

  • New Features

    • Updated versioning for multiple SDK packages to 1.0.0-rc.5.
  • Bug Fixes

    • Adjusted dependencies across various packages to ensure compatibility with the new version.
  • Chores

    • Removed the testing phase from the package preparation process, streamlining the release workflow.

@lucanicoladebiasi lucanicoladebiasi added this to the 1.1.0 milestone Dec 10, 2024
@lucanicoladebiasi lucanicoladebiasi self-assigned this Dec 10, 2024
@lucanicoladebiasi lucanicoladebiasi requested a review from a team as a code owner December 10, 2024 16:38
Copy link
Contributor

coderabbitai bot commented Dec 10, 2024

Walkthrough

The pull request includes updates to the package.json files across multiple projects and packages, incrementing version numbers from 1.0.0-rc.4 to 1.0.0-rc.5. This change affects both the main project versions and their respective dependencies, which have also been updated to the new version. Additionally, a modification in the scripts/pre-release.ts file removes the testing phase from the package preparation process, altering the control flow during package preparation.

Changes

File Path Change Summary
apps/sdk-cloudflare-integration/package.json Updated package version to 1.0.0-rc.5 and dependency @vechain/sdk-core to 1.0.0-rc.5.
apps/sdk-hardhat-integration/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core, @vechain/sdk-hardhat-plugin, and @vechain/sdk-logging to 1.0.0-rc.5.
apps/sdk-nextjs-integration/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core and @vechain/sdk-network to 1.0.0-rc.5.
apps/sdk-node-integration/package.json Updated package version to 1.0.0-rc.5 and dependency @vechain/sdk-network to 1.0.0-rc.5.
apps/sdk-vite-integration/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core and @vechain/sdk-network to 1.0.0-rc.5.
docs/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core and @vechain/sdk-network to 1.0.0-rc.5.
packages/aws-kms-adapter/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core, @vechain/sdk-errors, and @vechain/sdk-network to 1.0.0-rc.5.
packages/core/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-errors and @vechain/sdk-logging to 1.0.0-rc.5.
packages/errors/package.json Updated package version to 1.0.0-rc.5.
packages/ethers-adapter/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core, @vechain/sdk-errors, and @vechain/sdk-network to 1.0.0-rc.5.
packages/hardhat-plugin/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core, @vechain/sdk-errors, @vechain/sdk-ethers-adapter, @vechain/sdk-logging, and @vechain/sdk-network to 1.0.0-rc.5.
packages/logging/package.json Updated package version to 1.0.0-rc.5 and dependency @vechain/sdk-errors to 1.0.0-rc.5.
packages/network/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core, @vechain/sdk-errors, and @vechain/sdk-logging to 1.0.0-rc.5.
packages/rpc-proxy/package.json Updated package version to 1.0.0-rc.5 and dependencies @vechain/sdk-core, @vechain/sdk-errors, @vechain/sdk-logging, and @vechain/sdk-network to 1.0.0-rc.5.
scripts/pre-release.ts Removed the line executing await exec('yarn test:solo'); from the package preparation process.

Suggested reviewers

  • fabiorigam

🐰 In the meadow, hopping with glee,
Versions updated, oh what a spree!
From rc.4 to rc.5, we leap and bound,
Dependencies refreshed, joy abounds!
With testing removed, we dance through the night,
Celebrating changes, everything feels right! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 15f2a2b and b864c5f.

📒 Files selected for processing (15)
  • apps/sdk-cloudflare-integration/package.json (2 hunks)
  • apps/sdk-hardhat-integration/package.json (2 hunks)
  • apps/sdk-nextjs-integration/package.json (2 hunks)
  • apps/sdk-node-integration/package.json (2 hunks)
  • apps/sdk-vite-integration/package.json (2 hunks)
  • docs/package.json (2 hunks)
  • packages/aws-kms-adapter/package.json (2 hunks)
  • packages/core/package.json (2 hunks)
  • packages/errors/package.json (1 hunks)
  • packages/ethers-adapter/package.json (2 hunks)
  • packages/hardhat-plugin/package.json (2 hunks)
  • packages/logging/package.json (2 hunks)
  • packages/network/package.json (2 hunks)
  • packages/rpc-proxy/package.json (2 hunks)
  • scripts/pre-release.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • scripts/pre-release.ts
✅ Files skipped from review due to trivial changes (12)
  • packages/errors/package.json
  • apps/sdk-cloudflare-integration/package.json
  • apps/sdk-node-integration/package.json
  • apps/sdk-nextjs-integration/package.json
  • apps/sdk-vite-integration/package.json
  • packages/logging/package.json
  • docs/package.json
  • packages/core/package.json
  • apps/sdk-hardhat-integration/package.json
  • packages/network/package.json
  • packages/rpc-proxy/package.json
  • packages/hardhat-plugin/package.json
🔇 Additional comments (4)
packages/ethers-adapter/package.json (2)

3-3: LGTM: Version bump aligns with release candidate.

The version increment to 1.0.0-rc.5 follows semantic versioning and matches the PR objectives.


36-38: LGTM: Dependency versions are consistently updated.

The SDK dependencies (@vechain/sdk-core, @vechain/sdk-errors, @vechain/sdk-network) are correctly synchronized to version 1.0.0-rc.5, maintaining consistency across the ecosystem.

packages/aws-kms-adapter/package.json (2)

3-3: Verify version consistency across all packages

The version bump to 1.0.0-rc.5 should be consistent across all related packages in the VeChain SDK ecosystem.

✅ Verification successful

Version consistency verified across VeChain SDK packages

All packages in the VeChain SDK ecosystem are consistently versioned at 1.0.0-rc.5:

  • @vechain/sdk-aws-kms-adapter: 1.0.0-rc.5
  • @vechain/sdk-core: 1.0.0-rc.5
  • @vechain/sdk-network: 1.0.0-rc.5
  • @vechain/sdk-hardhat-plugin: 1.0.0-rc.5
  • @vechain/sdk-logging: 1.0.0-rc.5
  • @vechain/sdk-rpc-proxy: 1.0.0-rc.5
  • @vechain/sdk-ethers-adapter: 1.0.0-rc.5
  • @vechain/sdk-errors: 1.0.0-rc.5
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency across all package.json files
# Expected: All packages should be at version 1.0.0-rc.5

echo "Checking package versions..."
fd package.json --exec jq -r '. | select(.name | startswith("@vechain")) | [.name, .version] | @tsv'

Length of output: 445


43-45: Verify dependency updates and compatibility

The @vechain dependencies have been updated to match the new version. Let's verify:

  1. All @vechain dependencies are updated consistently
  2. Other fixed dependencies are secure and up-to-date
✅ Verification successful

Dependencies are consistent and secure

The verification shows:

  • All @vechain dependencies are consistently updated to version 1.0.0-rc.5 across the codebase
  • No security vulnerabilities found for ethers 6.13.4 or @aws-sdk/client-kms
  • The @aws-sdk/client-kms uses a caret range (^3.696.0) which is acceptable for AWS SDK
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check dependencies and security advisories

# Check for any @vechain dependencies that might still be on rc.4
echo "Checking for inconsistent @vechain dependencies..."
fd package.json --exec jq -r '.dependencies | to_entries[] | select(.key | startswith("@vechain")) | select(.value | contains("rc.4")) | [.key, .value] | @tsv'

# Check for security advisories for fixed dependencies
echo "Checking security advisories for ethers 6.13.4..."
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NPM, package: "ethers") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

echo "Checking security advisories for @aws-sdk/client-kms..."
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NPM, package: "@aws-sdk/client-kms") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

Length of output: 1326


Script:

#!/bin/bash
# Let's check all @vechain dependencies across package.json files
echo "Checking all @vechain dependencies..."
fd package.json --exec jq -r '
  if .dependencies then
    .dependencies | to_entries[] | select(.key | startswith("@vechain")) | [.key, .value] | @tsv
  else
    empty
  end'

# Let's also check the fixed versions of other dependencies in aws-kms-adapter
echo -e "\nChecking other dependencies in aws-kms-adapter..."
cat packages/aws-kms-adapter/package.json | jq -r '.dependencies | to_entries[] | select(.key | startswith("@aws-sdk") or .key == "ethers") | [.key, .value] | @tsv'

Length of output: 1677


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>, 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 generate docstrings to generate docstrings for this PR. (Experiment)
  • @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.

Copy link

Test Coverage

Summary

Lines Statements Branches Functions
Coverage: 99%
99% (4366/4410) 97.55% (1397/1432) 99.01% (906/915)
Title Tests Skipped Failures Errors Time
core 836 0 💤 0 ❌ 0 🔥 2m 22s ⏱️
network 727 0 💤 0 ❌ 0 🔥 5m 4s ⏱️
errors 42 0 💤 0 ❌ 0 🔥 16.893s ⏱️
logging 3 0 💤 0 ❌ 0 🔥 18.882s ⏱️
hardhat-plugin 19 0 💤 0 ❌ 0 🔥 59.99s ⏱️
aws-kms-adapter 23 0 💤 0 ❌ 0 🔥 1m 9s ⏱️
ethers-adapter 5 0 💤 0 ❌ 0 🔥 1m 14s ⏱️
rpc-proxy 37 0 💤 0 ❌ 0 🔥 1m 6s ⏱️

@freemanzMrojo freemanzMrojo merged commit 01c92c7 into main Dec 10, 2024
17 checks passed
@victhorbi victhorbi modified the milestones: 1.1.0 (Pre-Release), 2.0.0 Jan 8, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jan 31, 2025
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants