Skip to content

Update module go.yaml.in/yaml/v2 to v3#797

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/go.yaml.in-yaml-v2-3.x
Open

Update module go.yaml.in/yaml/v2 to v3#797
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/go.yaml.in-yaml-v2-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 7, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
go.yaml.in/yaml/v2 v2.4.3v3.0.4 age adoption passing confidence

Release Notes

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

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.4.4

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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


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

This PR was generated by Mend Renovate. View the repository job log.

@github-actions github-actions Bot added the chore Maintenance, refactor, or non-feature changes label Dec 7, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 7, 2025

MegaLinter analysis: Error

Descriptor Linter Files Fixed Errors Warnings Elapsed time
❌ BASH shellcheck 15 1 11 1.82s
✅ DOCKERFILE hadolint 3 0 0 0.36s
✅ JSON jsonlint 18 0 0 0.47s
⚠️ MARKDOWN markdownlint 18 2 28 0 2.19s
✅ REPOSITORY secretlint yes no no 5.91s
⚠️ SQL sqlfluff 2 0 1 0 4.4s
✅ YAML yamllint 54 0 0 4.31s

Detailed Issues

❌ BASH / shellcheck - 1 error
note: Modification of VIOLATIONS is local (to subshell caused by pipeline).
   ┌─ frontend/scripts/check-shadcn-compliance.sh:45:9
   │
45 │         VIOLATIONS=$((VIOLATIONS + 1))
   │         ^^^^^^^^^^
   │
   = SC2030
   = For more information: https://www.shellcheck.net/wiki/SC2030

warning: Use 'find .. -print0 | xargs -0 ..' or 'find .. -exec .. +' to allow non-alphanumeric filenames.
   ┌─ frontend/scripts/check-shadcn-compliance.sh:74:18
   │
74 │   dialog_files=$(find src/components -name "*.tsx" ! -name "*.test.tsx" ! -path "*/ui/*" | \
   │                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   │
   = SC2038
   = For more information: https://www.shellcheck.net/wiki/SC2038

note: VIOLATIONS was modified in a subshell. That change might be lost.
   ┌─ frontend/scripts/check-shadcn-compliance.sh:93:21
   │
93 │       VIOLATIONS=$((VIOLATIONS + 1))
   │                     ^^^^^^^^^^
   │
   = SC2031
   = For more information: https://www.shellcheck.net/wiki/SC2031

warning: Use 'find .. -print0 | xargs -0 ..' or 'find .. -exec .. +' to allow non-alphanumeric filenames.
    ┌─ frontend/scripts/check-shadcn-compliance.sh:100:15
    │
100 │ UI_ELEMENTS=$(find src/components/ui -name "*.tsx" ! -name "*.test.tsx" ! -name "input.tsx" ! -name "textarea.tsx" ! -name "button.tsx" ! -name "sidebar.tsx" | \
    │               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    │
    = SC2038
    = For more information: https://www.shellcheck.net/wiki/SC2038

note: Modification of VIOLATIONS is local (to subshell caused by pipeline).
   ┌─ frontend/scripts/check-frontend-docs.sh:19:5
   │
19 │     VIOLATIONS=$((VIOLATIONS + 1))
   │     ^^^^^^^^^^
   │
   = SC2030
   = For more information: https://www.shellcheck.net/wiki/SC2030

note: VIOLATIONS was modified in a subshell. That change might be lost.
   ┌─ frontend/scripts/check-frontend-docs.sh:45:13
   │
45 │       if [ "$VIOLATIONS" -eq 0 ]; then
   │             ^^^^^^^^^^^
   │
   = SC2031
   = For more information: https://www.shellcheck.net/wiki/SC2031

note: See if you can use ${variable//search/replace} instead.
   ┌─ frontend/scripts/check-frontend-docs.sh:52:20
   │
52 │         rel_path=$(echo "$file" | sed "s|src/$dir/||")
   │                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   │
   = SC2001
   = For more information: https://www.shellcheck.net/wiki/SC2001

note: Modification of VIOLATIONS is local (to subshell caused by pipeline).
   ┌─ frontend/scripts/check-frontend-docs.sh:54:9
   │
54 │         VIOLATIONS=$((VIOLATIONS + 1))
   │         ^^^^^^^^^^
   │
   = SC2030
   = For more information: https://www.shellcheck.net/wiki/SC2030

note: VIOLATIONS was modified in a subshell. That change might be lost.
   ┌─ frontend/scripts/check-frontend-docs.sh:54:23
   │
54 │         VIOLATIONS=$((VIOLATIONS + 1))
   │                       ^^^^^^^^^^
   │
   = SC2031
   = For more information: https://www.shellcheck.net/wiki/SC2031

note: VIOLATIONS was modified in a subshell. That change might be lost.
   ┌─ frontend/scripts/check-frontend-docs.sh:68:7
   │
68 │ if [ "$VIOLATIONS" -gt 0 ]; then
   │       ^^^^^^^^^^^
   │
   = SC2031
   = For more information: https://www.shellcheck.net/wiki/SC2031

note: VIOLATIONS was modified in a subshell. That change might be lost.
   ┌─ frontend/scripts/check-frontend-docs.sh:73:15
   │
73 │   echo "Found $VIOLATIONS prohibited documentation file(s)"
   │               ^^^^^^^^^^^
   │
   = SC2031
   = For more information: https://www.shellcheck.net/wiki/SC2031

warning: 2 warnings emitted
⚠️ MARKDOWN / markdownlint - 28 errors
AGENTS.md:125 error MD025/single-title/single-h1 Multiple top-level headings in the same document [Context: "📋 ENFORCEMENT MECHANISMS SUMM..."]
docs/ai-prompt-frontend-cleanup.md:402:9 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:402:18 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:402:32 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:402:1 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:402:9 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:402:18 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:9 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:20 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:34 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:48 error MD060/table-column-style Table column style [Table pipe is missing space to the left for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:1 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:9 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:20 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:676:34 error MD060/table-column-style Table column style [Table pipe is missing space to the right for style "compact"]
docs/ai-prompt-frontend-cleanup.md:739 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
docs/README.md:43:30 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:43:81 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:44:26 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:44:77 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:45:26 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:45:77 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:46:26 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:46:77 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:47:26 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:47:77 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:48:26 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/README.md:48:77 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
⚠️ SQL / sqlfluff - 1 error
WARNING: Config file .github/linters/.sqlfluff set a deprecated config value `rules:max_line_length`. This will be removed in a later release. This has been mapped to `max_line_length` set to a value of 120 for this run. Please update your configuration to remove this warning. 

The max_line_length config has moved from sqlfluff:rules to the root sqlfluff level.

See https://docs.sqlfluff.com/en/stable/perma/configuration.html for more details.

==== finding fixable violations ====
WARNING    Rule configuration contain a section for unexpected rule 'L010'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP01 with name 'capitalisation.keywords'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.keywords'. 
WARNING    Rule configuration contain a section for unexpected rule 'L014'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP02 with name 'capitalisation.identifiers'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.identifiers'. 
WARNING    Rule configuration contain a section for unexpected rule 'L030'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP03 with name 'capitalisation.functions'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.functions'. 
== [backend/config/postgres_security.sql] FAIL
L:   5 | P:   1 |  PRS | Line 5, Position 1: Found unparsable section: 'ALTER
                       | SYSTEM SET ssl = on;\nALTER SYSTEM ...'
WARNING    Rule configuration contain a section for unexpected rule 'L010'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP01 with name 'capitalisation.keywords'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.keywords'. 
WARNING    Rule configuration contain a section for unexpected rule 'L014'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP02 with name 'capitalisation.identifiers'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.identifiers'. 
WARNING    Rule configuration contain a section for unexpected rule 'L030'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP03 with name 'capitalisation.functions'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.functions'. 
==== no fixable linting violations found ====
All Finished!
==== lint for unfixable violations ====
== [backend/config/postgres_security.sql] PASS
== [backend/scripts/reset-mfa.sql] PASS

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.3.0 --custom-flavor-setup --custom-flavor-linters BASH_SHELLCHECK,DOCKERFILE_HADOLINT,JSON_JSONLINT,MARKDOWN_MARKDOWNLINT,REPOSITORY_SECRETLINT,SQL_SQLFLUFF,YAML_YAMLLINT

MegaLinter is graciously provided by OX Security

@renovate renovate Bot force-pushed the renovate/go.yaml.in-yaml-v2-3.x branch from e6c6e16 to 95396ac Compare December 15, 2025 16:46
@renovate renovate Bot force-pushed the renovate/go.yaml.in-yaml-v2-3.x branch from 95396ac to a0e446f Compare February 2, 2026 14:59
@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.55%. Comparing base (c272d12) to head (a0e446f).

❌ Your project check has failed because the head coverage (72.85%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #797   +/-   ##
=======================================
  Coverage   61.55%   61.55%           
=======================================
  Files         167      167           
  Lines       12714    12714           
  Branches      879      879           
=======================================
  Hits         7826     7826           
  Misses       4256     4256           
  Partials      632      632           
Flag Coverage Δ
backend 56.69% <ø> (ø)
frontend 72.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c272d12...a0e446f. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate Bot changed the title chore(deps): update module go.yaml.in/yaml/v2 to v3 Update module go.yaml.in/yaml/v2 to v3 Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Maintenance, refactor, or non-feature changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants