Upgrade dependencies

[Danielius1922]

Summary by CodeRabbit

• Chores
  • Updated dependencies and actions for better performance and compatibility.
  • Improved CI/CD workflows for building and testing.
  • Enhanced code linting settings for more robust code quality checks.

[coderabbitai]

Walkthrough

This summary outlines updates to GitHub Actions and dependency configurations across several workflows and project files. Notably, it includes version upgrades for GitHub Actions like goreleaser/goreleaser-action and golangci/golangci-lint-action, tweaks to workflow arguments, and the addition of a configuration for gomoddirectives. Also, it details an update to the commit hash for the googleapis subproject.

Changes

File Path	Change Summary
.github/workflows/buildTestBinaries.yml	Updated goreleaser-action to v5; Modified arguments for Build client
.github/workflows/golangci-lint.yml	Updated golangci-lint-action to v4; Added --timeout=5m arg
.golangci.yml	Added gomoddirectives config for github.com/pion/dtls/v2
dependency/googleapis	Updated subproject commit hash
web/playwright/.github/workflows/playwright.yml	Updated upload-artifact to v4

Related issues

• plgd-dev/device-provisioning-service#217: The updates to GitHub Actions and dependencies may align with the objectives of updating various dependencies and GitHub Actions versions.
• Dependency Dashboard #6: The updates to GitHub Actions versions and the addition of specific configurations might address some of the dependency and GitHub Actions updates outlined.

🐰✨
Changes abound, in files and lines,
Where versions leap, and code aligns.
Through workflows, lints, and directives new,
A rabbit hops, leaving tracks so true.
🌟📦🔧

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-tests 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 tests 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 tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 5d3732f and 3610091.

Files ignored due to path filters (2)

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

Files selected for processing (5)

• .github/workflows/buildTestBinaries.yml (1 hunks)
• .github/workflows/golangci-lint.yml (1 hunks)
• .golangci.yml (1 hunks)
• dependency/googleapis (1 hunks)
• web/playwright/.github/workflows/playwright.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• dependency/googleapis

Additional comments: 5

web/playwright/.github/workflows/playwright.yml (1)

• 22-22: The update of actions/upload-artifact from v3 to v4 is correctly applied and follows best practices for keeping dependencies up-to-date. Ensure that this version change is tested to confirm compatibility with the rest of the workflow.

.github/workflows/golangci-lint.yml (1)

• 30-30: The update of golangci/golangci-lint-action from v3 to v4 and the addition of args: --timeout=5m are correctly applied. These changes are expected to enhance the linting process's efficiency. It's important to verify that the new timeout setting aligns with the project's requirements and does not inadvertently cut off necessary linting operations.

.github/workflows/buildTestBinaries.yml (2)

• 44-44: The update of goreleaser/goreleaser-action to v5 is correctly applied. This version update is crucial for leveraging the latest features and improvements of goreleaser.
• 48-48: The modification of arguments to release --clean --skip=validate --skip=publish aligns with the objective to optimize the build process. However, ensure that skipping validation and publishing steps is intentional and does not impact the project's release or distribution process.

.golangci.yml (1)

• 8-10: The addition of gomoddirectives configuration with github.com/pion/dtls/v2 in the replace-allow-list is correctly applied. This configuration ensures that the specified dependency is correctly handled during the linting process, which can improve the project's code quality and maintainability. It's important to verify that this inclusion aligns with the project's dependency management strategy.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud