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

fix(deps): update module gopkg.in/yaml.v2 to v3 - autoclosed #2235

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
gopkg.in/yaml.v2 v2.4.0 -> v3.0.1 age adoption passing confidence
gopkg.in/yaml.v2 v2.2.8 -> v3.0.1 age adoption passing confidence

Release Notes

go-yaml/yaml (gopkg.in/yaml.v2)

v3.0.1

Compare Source

v3.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the 🤖 Dependencies Pull requests that update a dependency file label Feb 22, 2024
@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch 4 times, most recently from 3465676 to 78205c2 Compare February 25, 2024 19:42
Copy link
Contributor Author

renovate bot commented Feb 26, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: aws-sam/app/go.sum
Command failed: go get -d -t ./...
go: errors parsing go.mod:
go.mod:21: replace gopkg.in/yaml.v2: version "v3.0.1" invalid: should be v2, not v3

@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch from 78205c2 to ccb34bf Compare February 26, 2024 07:39
@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch from ccb34bf to 3c166e9 Compare March 12, 2024 14:19
Copy link
Contributor

coderabbitai bot commented Mar 12, 2024

Important

Review skipped

Ignore keyword(s) in the title.

Ignored keywords (4)
  • (deps)
  • build(deps)
  • bumb
  • fix(deps)

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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

@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch 3 times, most recently from 7119256 to 174fc28 Compare March 19, 2024 07:32
@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch from 174fc28 to 2e3ee74 Compare April 2, 2024 12:04
@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch 3 times, most recently from 580217a to 80d4266 Compare May 1, 2024 14:49
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: aws-sam/app/go.sum
Command failed: go get -d -t ./...
go: errors parsing go.mod:
go.mod:21: replace gopkg.in/yaml.v2: version "v3.0.1" invalid: should be v2, not v3

| datasource | package          | from   | to     |
| ---------- | ---------------- | ------ | ------ |
| go         | gopkg.in/yaml.v2 | v2.4.0 | v3.0.1 |
| go         | gopkg.in/yaml.v2 | v2.2.8 | v3.0.1 |
@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch from 80d4266 to 7c95867 Compare June 26, 2024 18:06
@renovate renovate bot changed the title fix(deps): update module gopkg.in/yaml.v2 to v3 fix(deps): update module gopkg.in/yaml.v2 to v3 - autoclosed Jun 27, 2024
@renovate renovate bot closed this Jun 27, 2024
@renovate renovate bot deleted the renovate/gopkg.in-yaml.v2-3.x branch June 27, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 Dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant