Upgrade dependencies

[Danielius1922]

Direct:
github.com/fxamacker/cbor/v2 v2.7.0
github.com/jessevdk/go-flags v1.6.1
github.com/pion/dtls/v2 v2.2.8-0.20240701035148-45e16a098c47
github.com/plgd-dev/go-coap/v3 v3.3.5-0.20240702075841-0340410d65ba

Indirect:
golang.org/x/crypto v0.24.0
golang.org/x/exp v0.0.0-20240613232115-7f521ea00fb8
golang.org/x/net v0.26.0
golang.org/x/sys v0.21.0
google.golang.org/genproto/googleapis/rpc v0.0.0-20240701130421-f6361c86f094
google.golang.org/protobuf v1.34.2

Summary by CodeRabbit

• Chores

  • Updated Docker build and push action to latest version for improved reliability and features.

• Dependencies

  • Upgraded multiple Go module dependencies to their latest versions for enhanced security, performance, and compatibility.

[coderabbitai]

Walkthrough

The recent updates primarily involve version upgrades for various dependencies in the go.mod file and a minor revision of a GitHub Actions configuration file. The docker/build-push-action was updated from v5 to v6, and several Go dependencies were bumped to newer versions for better functionality, stability, and security.

Changes

Files	Summary of Changes
.github/.../build-publish-cfg.yaml	Updated docker/build-push-action from v5 to v6
go.mod	Various dependency version updates

Poem

In the forest of code where updates bloom,
New versions rise, dispelling gloom.
Docker steps up with a push anew,
While Go's dependencies shine bright and true.
A rabbit hops through lines of lore,
Celebrating tweaks that help us soar.
🐇✨

---

Tip

Early access features: enabled

We are currently testing the following features in early access:

• OpenAI gpt-4o model for code reviews and chat: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues.
• OSS projects are currently opted into early access features by default.

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.87%. Comparing base (6c9b1dc) to head (19f5cca).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #480      +/-   ##
==========================================
+ Coverage   76.85%   76.87%   +0.01%     
==========================================
  Files         121      121              
  Lines        7225     7225              
==========================================
+ Hits         5553     5554       +1     
  Misses       1084     1084              
+ Partials      588      587       -1     

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6c9b1dc and 19f5cca.

Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

Files selected for processing (2)

• .github/workflows/build-publish-cfg.yaml (2 hunks)
• go.mod (2 hunks)

Files skipped from review due to trivial changes (1)

• go.mod

Additional comments not posted (2)

.github/workflows/build-publish-cfg.yaml (2)

91-91: Verify compatibility of docker/build-push-action@v6.

Ensure that the upgrade from v5 to v6 does not introduce any breaking changes or compatibility issues with your workflow.

Verification successful

---

Verified compatibility of docker/build-push-action@v6.

The upgrade from v5 to v6 introduces a new feature for generating build summaries and exporting build records. This feature can be disabled by setting the DOCKER_BUILD_NO_SUMMARY: true environment variable in your workflow. No breaking changes were identified.

• Ensure your workflow accounts for the new build summary feature if necessary.

Scripts executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify compatibility of `docker/build-push-action@v6`.

# Test: Check the changelog for breaking changes. Expect: No breaking changes.
curl -s https://raw.githubusercontent.com/docker/build-push-action/main/CHANGELOG.md | grep -A 10 "v6.0.0"

Length of output: 106

---

---

Script:

#!/bin/bash
# Description: Verify compatibility of `docker/build-push-action@v6`.

# Fetch the release notes for docker/build-push-action@v6 from the GitHub releases page.
curl -s https://api.github.com/repos/docker/build-push-action/releases/tags/v6.0.0 | jq '.body'

Length of output: 1083

---

115-115: Verify compatibility of docker/build-push-action@v6.

Ensure that the upgrade from v5 to v6 does not introduce any breaking changes or compatibility issues with your workflow.

Verification successful

---

The upgrade to docker/build-push-action@v6 introduces new features for generating build summaries and exporting build records. There are no breaking changes listed that would impact your existing workflow.

• You can disable the new build summary feature by setting the DOCKER_BUILD_NO_SUMMARY: true environment variable if it is not needed.

Scripts executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify compatibility of `docker/build-push-action@v6`.

# Test: Check the changelog for breaking changes. Expect: No breaking changes.
curl -s https://raw.githubusercontent.com/docker/build-push-action/main/CHANGELOG.md | grep -A 10 "v6.0.0"

Length of output: 106

---

---

Script:

#!/bin/bash
# Ensure the changelog file exists and fetch its contents
curl -s https://raw.githubusercontent.com/docker/build-push-action/main/CHANGELOG.md -o CHANGELOG.md

# Check if the changelog file contains the v6.0.0 release notes
if grep -q "## \[v6.0.0\]" CHANGELOG.md; then
  # Extract the v6.0.0 release notes and display them
  sed -n '/## \[v6.0.0\]/,/## \[v/p' CHANGELOG.md
else
  echo "v6.0.0 release notes not found in the changelog."
fi

Length of output: 248

---

---

Script:

#!/bin/bash
# Fetch the release notes for v6.0.0 from the GitHub releases page
curl -s https://api.github.com/repos/docker/build-push-action/releases/tags/v6.0.0 | jq -r '.body'

Length of output: 1070