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

chore(devcontainer): update image: v1.1.0 #2960

Merged
merged 1 commit into from
Jan 28, 2025
Merged

chore(devcontainer): update image: v1.1.0 #2960

merged 1 commit into from
Jan 28, 2025

Conversation

tarrencev
Copy link
Contributor

@tarrencev tarrencev commented Jan 28, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Chores
    • Updated development and CI container images from commit-specific tag b37b325 to version tag v1.1.0
    • Updated container images in DevContainer configuration, GitHub Actions workflows for benchmarking, continuous integration, and release dispatch

Copy link

coderabbitai bot commented Jan 28, 2025

Walkthrough

Ohayo, sensei! This pull request focuses on updating the Docker image version across multiple configuration files from a specific commit hash b37b325 to a tagged version v1.1.0. The changes are consistent across the development container configuration (.devcontainer/devcontainer.json) and various GitHub Actions workflow files, including bench.yml, ci.yml, and release-dispatch.yml. This update ensures a standardized and versioned container environment for development and CI/CD processes.

Changes

File Change Summary
.devcontainer/devcontainer.json Updated Docker image from b37b325 to v1.1.0
.github/workflows/bench.yml Updated container images for bench-katana and bench-sozo jobs from b37b325 to v1.1.0
.github/workflows/ci.yml Updated container images for multiple jobs (build, test, ensure-wasm, clippy, fmt, docs) from b37b325 to v1.1.0
.github/workflows/release-dispatch.yml Updated container image for propose-release job from b37b325 to v1.1.0

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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: 1

🧹 Nitpick comments (1)
.github/workflows/bench.yml (1)

17-17: Consider documenting version update impact.

Since this is a version update that affects both benchmark jobs, it would be helpful to document any significant changes or improvements in the new image version that might impact the benchmark results.

Also applies to: 39-39

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dd7e42d and 79c94f6.

📒 Files selected for processing (4)
  • .devcontainer/devcontainer.json (1 hunks)
  • .github/workflows/bench.yml (2 hunks)
  • .github/workflows/ci.yml (6 hunks)
  • .github/workflows/release-dispatch.yml (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • .github/workflows/ci.yml
  • .github/workflows/release-dispatch.yml
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: clippy
🔇 Additional comments (2)
.github/workflows/bench.yml (2)

17-17: LGTM! Version update for bench-katana job.

The Docker image version is consistent with the devcontainer configuration.


39-39: LGTM! Version update for bench-sozo job.

The Docker image version is consistent with the devcontainer configuration.

@@ -2,7 +2,7 @@
// https://github.com/microsoft/vscode-dev-containers/tree/v0.245.2/containers/rust
{
"name": "Rust",
"image": "ghcr.io/dojoengine/dojo-dev:b37b325",
"image": "ghcr.io/dojoengine/dojo-dev:v1.1.0",
Copy link

Choose a reason for hiding this comment

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

💡 Codebase verification

Ohayo sensei! The Docker image version v1.1.0 does not exist! 🚨

The specified version v1.1.0 is not available in the container registry. The latest semantic version available is v0.1.0. Please either:

  • Use an existing version (e.g., v0.1.0 or latest)
  • Consult with the Dojo team about the correct version to use
🔗 Analysis chain

Ohayo sensei! Let's verify the Docker image version.

The change from commit hash b37b325 to semantic version v1.1.0 is a good practice for better version tracking.

Let's confirm that this version exists and is stable:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

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

# Check if the image exists and get its details
curl -s -H "Authorization: Bearer $(curl -s "https://ghcr.io/token?scope=repository:dojoengine/dojo-dev:pull" | jq -r .token)" \
  https://ghcr.io/v2/dojoengine/dojo-dev/manifests/v1.1.0 | jq .

# Get the image creation date and other metadata
curl -s -H "Authorization: Bearer $(curl -s "https://ghcr.io/token?scope=repository:dojoengine/dojo-dev:pull" | jq -r .token)" \
  https://ghcr.io/v2/dojoengine/dojo-dev/tags/list | jq '.tags[]'

Length of output: 4030

Copy link

codecov bot commented Jan 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.72%. Comparing base (dd7e42d) to head (79c94f6).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2960   +/-   ##
=======================================
  Coverage   56.71%   56.72%           
=======================================
  Files         420      420           
  Lines       55557    55557           
=======================================
+ Hits        31507    31512    +5     
+ Misses      24050    24045    -5     

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

@glihm glihm merged commit 384e3d8 into main Jan 28, 2025
15 checks passed
@glihm glihm deleted the bump-devcontainer branch January 28, 2025 16:52
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