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

Update devcontainer image: v1.0.2 #2723

Merged
merged 1 commit into from
Nov 26, 2024
Merged

Update devcontainer image: v1.0.2 #2723

merged 1 commit into from
Nov 26, 2024

Conversation

tarrencev
Copy link
Contributor

@tarrencev tarrencev commented Nov 26, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Updated Docker image version to enhance the development environment and CI pipeline.
  • Chores

    • Modified multiple GitHub Actions workflows to use the new Docker image version for various jobs, ensuring consistency across the environment.

Copy link

coderabbitai bot commented Nov 26, 2024

Walkthrough

Ohayo, sensei! This pull request updates the Docker image version across several configuration files related to a Rust development environment. The image version has been changed from v1.0.1 to v1.0.2 in the .devcontainer/devcontainer.json, GitHub Actions workflows for benchmarking, CI, and release dispatch. Additionally, the CI workflow introduces a new step to handle built binaries. Overall, these changes ensure that the development and CI environments utilize the latest Docker image.

Changes

File Change Summary
.devcontainer/devcontainer.json Updated Docker image version from v1.0.1 to v1.0.2.
.github/workflows/bench.yml Updated Docker image version from v1.0.1 to v1.0.2 in bench-katana and bench-sozo jobs.
.github/workflows/ci.yml Updated Docker image version from v1.0.1 to v1.0.2 in multiple jobs; added step for bins directory.
.github/workflows/release-dispatch.yml Updated Docker image version from v1.0.1 to v1.0.2 in propose-release job.

Possibly related PRs

Suggested reviewers

  • glihm

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

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

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
.github/workflows/bench.yml (1)

Line range hint 17-39: Consider documenting version dependencies, sensei!

Since this is a development environment update, it would be helpful to document any significant changes or dependencies introduced in v1.0.2 that might affect the benchmark results.

Would you like me to help create a documentation template or open an issue to track this?

🧰 Tools
🪛 actionlint (1.7.4)

19-19: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8eb8c48 and 1fbbad7.

📒 Files selected for processing (4)
  • .devcontainer/devcontainer.json (1 hunks)
  • .github/workflows/bench.yml (2 hunks)
  • .github/workflows/ci.yml (7 hunks)
  • .github/workflows/release-dispatch.yml (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .devcontainer/devcontainer.json
🔇 Additional comments (5)
.github/workflows/release-dispatch.yml (2)

17-17: Ohayo sensei! The Docker image version update looks good!

The bump from v1.0.1 to v1.0.2 aligns with the changes across other configuration files in the PR.


17-17: Verify the Docker image availability

Let's ensure the new image version exists and is properly tagged in the container registry.

✅ Verification successful

Docker image ghcr.io/dojoengine/dojo-dev:v1.0.2 is available and properly tagged

The image exists in the container registry and is tagged with both v1.0.2 and latest. The image was published on November 26, 2024, and is ready for use.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the Docker image exists and is properly tagged
# Expected result: The image should exist and be tagged with v1.0.2

# Check if the image exists and get its details
gh api \
  -H "Accept: application/vnd.github+json" \
  "/users/dojoengine/packages/container/dojo-dev/versions" | \
  jq '.[] | select(.metadata.container.tags[] | contains("v1.0.2"))'

Length of output: 782

.github/workflows/bench.yml (1)

17-17: Ohayo! Let's verify the new image version, sensei!

The update to v1.0.2 looks good, but let's ensure the image is properly tagged and available.

Also applies to: 39-39

✅ Verification successful

Ohayo sensei! The image version is properly tagged and fresh! ✨

The v1.0.2 image was created on November 26, 2024, and is also tagged as latest, confirming it's the most recent version. The image exists in the registry and is ready for use in the workflow.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the Docker image version exists and check its creation date

# Check if the image exists and when it was created
gh api \
  -H "Accept: application/vnd.github+json" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  /orgs/dojoengine/packages/container/dojo-dev/versions \
  --jq '.[] | select(.metadata.container.tags[] == "v1.0.2") | {created_at: .created_at, tags: .metadata.container.tags}'

Length of output: 326

.github/workflows/ci.yml (2)

Line range hint 13-22: Ohayo sensei! Clean artifact organization implemented.

The new binary handling approach with a dedicated bins directory and explicit copying of katana and sozo binaries improves artifact organization and clarity.

🧰 Tools
🪛 actionlint (1.7.4)

32-32: label "ubuntu-latest-32-cores" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)


36-36: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


34-34: Verify Docker image version update implications

The Docker image ghcr.io/dojoengine/dojo-dev has been consistently updated to v1.0.2 across all jobs. Let's verify the version and check for any breaking changes.

Also applies to: 59-59, 126-126, 142-142, 157-157, 166-166, 175-175

✅ Verification successful

Docker image update to v1.0.2 looks good

Ohayo sensei! The update to v1.0.2 is verified and safe to proceed. The changelog shows this is a stable release with multiple improvements and bug fixes, including:

  • DevContainer image updates
  • Various Torii improvements (CLI, GraphQL, SQL)
  • Katana enhancements
  • Bug fixes and refactoring

The version is consistently updated across all jobs and the changes are non-breaking improvements.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify Docker image version and changes

# Check if v1.0.2 is the latest tag
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/dojoengine/dojo/packages/container/dojo-dev/versions \
  --jq 'map(select(.metadata.container.tags[] | contains("v1.0"))) | sort_by(.created_at) | reverse | .[0].metadata.container.tags'

# Check for changelog or release notes
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/dojoengine/dojo/releases/tags/v1.0.2 \
  --jq '.body'

Length of output: 2532

Copy link

codecov bot commented Nov 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.25%. Comparing base (8eb8c48) to head (1fbbad7).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2723      +/-   ##
==========================================
+ Coverage   56.24%   56.25%   +0.01%     
==========================================
  Files         415      415              
  Lines       53206    53206              
==========================================
+ Hits        29927    29933       +6     
+ Misses      23279    23273       -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@glihm glihm merged commit cc82661 into main Nov 26, 2024
14 checks passed
@glihm glihm deleted the bump-devcontainer branch November 26, 2024 13:43
augustin-v pushed a commit to augustin-v/dojo that referenced this pull request Dec 4, 2024
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.

2 participants