Skip to content

build(deps): Upgrade to outcome v2.2.12.#879

Merged
LinZhihao-723 merged 1 commit into
y-scope:mainfrom
LinZhihao-723:outcome-update
May 5, 2025
Merged

build(deps): Upgrade to outcome v2.2.12.#879
LinZhihao-723 merged 1 commit into
y-scope:mainfrom
LinZhihao-723:outcome-update

Conversation

@LinZhihao-723

@LinZhihao-723 LinZhihao-723 commented May 5, 2025

Copy link
Copy Markdown
Member

Description

This PR updates outcome to the latest release to fix the clang-tidy issue discussed here.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

  • Ensure all workflows passed.

Summary by CodeRabbit

  • Chores
    • Updated the outcome dependency to version v2.2.12.

@LinZhihao-723 LinZhihao-723 requested a review from a team as a code owner May 5, 2025 17:52
@coderabbitai

coderabbitai Bot commented May 5, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The change updates the outcome dependency in the taskfiles/deps/main.yaml configuration file. The version of the outcome library is upgraded from v2.2.9 to v2.2.12, and the corresponding SHA256 checksum for the tarball is replaced to match the new version. No other modifications are made to the file or its logic.

Changes

File(s) Change Summary
taskfiles/deps/main.yaml Updated the outcome dependency version from v2.2.9 to v2.2.12 and changed its SHA256 hash.

Sequence Diagram(s)

No sequence diagram is generated as the change is limited to a dependency version and checksum update without affecting control flow or feature logic.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 257c0fb and 3f0c4c7.

📒 Files selected for processing (1)
  • taskfiles/deps/main.yaml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: ubuntu-jammy-dynamic-linked-bins
  • GitHub Check: ubuntu-jammy-static-linked-bins
  • GitHub Check: ubuntu-jammy-lint
  • GitHub Check: centos-stream-9-dynamic-linked-bins
  • GitHub Check: centos-stream-9-static-linked-bins
  • GitHub Check: build-macos (macos-13, true)
  • GitHub Check: build-macos (macos-13, false)
🔇 Additional comments (2)
taskfiles/deps/main.yaml (2)

219-219: Approve version bump in download URL.

The download URL has been correctly updated from v2.2.9 to v2.2.12 for the outcome library. This aligns with the PR objective to address the clang-tidy issue.


210-210:

Details

❓ Verification inconclusive

Verify updated checksum for outcome v2.2.12.

The SHA256 checksum has been updated to match the v2.2.12 tarball. Please confirm it by downloading the archive and computing its hash.


🏁 Script executed:

#!/bin/bash
# Description: Download the outcome v2.2.12 tarball and verify its SHA256 checksum.
URL="https://github.com/ned14/outcome/archive/refs/tags/v2.2.12.tar.gz"
EXPECTED="14e15bda4e7c26ee42b0329d7ff746235f67bda084305c9d61297e9a521deb18"
ACTUAL=$(curl -sL "$URL" | sha256sum | awk '{print $1}')
if [ "$ACTUAL" != "$EXPECTED" ]; then
  echo "Checksum mismatch: expected $EXPECTED, got $ACTUAL"
  exit 1
fi
echo "Checksum verified successfully: $ACTUAL"

Length of output: 667


🏁 Script executed:

#!/bin/bash
# Description: Download the outcome v2.2.12 tarball and verify its SHA256 checksum using Python.
URL="https://github.com/ned14/outcome/archive/refs/tags/v2.2.12.tar.gz"
EXPECTED="14e15bda4e7c26ee42b0329d7ff746235f67bda084305c9d61297e9a521deb18"
# Compute actual checksum with Python
ACTUAL=$(curl -sL "$URL" | python3 - << 'EOF'
import sys, hashlib
data = sys.stdin.buffer.read()
print(hashlib.sha256(data).hexdigest())
EOF
)
if [ "$ACTUAL" != "$EXPECTED" ]; then
  echo "Checksum mismatch: expected $EXPECTED, got $ACTUAL"
  exit 1
fi
echo "Checksum verified successfully: $ACTUAL"

Length of output: 801


Checksum verification inconclusive – please perform a manual check
The automated scripts in this environment did not retrieve the archive data, resulting in an empty‐file hash. Please download the v2.2.12 tarball directly and run a local sha256sum (or equivalent) against the file to confirm that it matches 14e15bda4e7c26ee42b0329d7ff746235f67bda084305c9d61297e9a521deb18.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

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

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@kirkrodrigues kirkrodrigues changed the title build: Update outcome to the latest release. build(deps): Update outcome to v2.2.12. May 5, 2025
@kirkrodrigues kirkrodrigues changed the title build(deps): Update outcome to v2.2.12. build(deps): Upgrade to outcome v2.2.12. May 5, 2025

@kirkrodrigues kirkrodrigues left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Edited the PR title directly. Wait for CI to pass before merging.

@LinZhihao-723 LinZhihao-723 merged commit 64aebfe into y-scope:main May 5, 2025
26 of 29 checks passed
junhaoliao pushed a commit to junhaoliao/clp that referenced this pull request May 17, 2026
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