Skip to content

chore: update versions #1198

chore: update versions

chore: update versions #1198

Workflow file for this run

---
# SPDX-license-identifier: Apache-2.0
##############################################################################
# Copyright (c) 2020
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Apache License, Version 2.0
# which accompanies this distribution, and is available at
# http://www.apache.org/licenses/LICENSE-2.0
##############################################################################
name: Lint Code Base
# yamllint disable-line rule:truthy
on:
push:
pull_request:
jobs:
get-sloc:
name: Count Lines of Code
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # 6.0.2
with:
persist-credentials: false
- name: Setup Go
uses: actions/setup-go@7a3fe6cf4cb3a834922a1244abfce67bcef6a0c5 # 6.2.0
with:
go-version: ">=1.20.0"
- name: Install dependencies
run: go install github.com/boyter/scc/v3@latest
- name: Run scc tool
run: scc --format wide
check-broken-links:
name: Check documentation external links
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # 6.0.2
with:
persist-credentials: false
- name: Check broken links
uses: tcort/github-action-markdown-link-check@e7c7a18363c842693fadde5d41a3bd3573a7a225 # 1.1.2
check-super-linter:
name: Check syntax (super-linter)
runs-on: ubuntu-latest
permissions:
contents: read
packages: read
statuses: write
models: read
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # 6.0.2
with:
fetch-depth: 0
persist-credentials: false
- name: Run super-linter validation
uses: super-linter/super-linter@61abc07d755095a68f4987d1c2c3d1d64408f1f9 # 8.5.0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
LINTER_RULES_PATH: /
VALIDATE_JSCPD: false
VALIDATE_SHELL_SHFMT: false
VALIDATE_CHECKOV: false
VALIDATE_BIOME_LINT: false
VALIDATE_BIOME_FORMAT: false
VALIDATE_ENV: false
VALIDATE_PYTHON_RUFF_FORMAT: false
EDITORCONFIG_FILE_NAME: .editorconfig-checker.json
KUBERNETES_KUBECONFORM_OPTIONS: "-ignore-missing-schemas -ignore-filename-pattern custom-rules.yml"
DEFAULT_BRANCH: ${{ github.head_ref || github.ref_name }}
- uses: GrantBirki/git-diff-action@7420e4d095c27bb23359787640976d60c94fd216 # 2.8.1
id: git-diff
if: failure()
- name: Get failed linter logs
id: get-failed-linters
if: failure()
run: |
find ./super-linter-output/super-linter/ -name '*.json' -exec sh -c 'jq -e ".Exitval != 0" "$1" >/dev/null && printf "%s\0" "$1"' _ {} \; | xargs -0 jq -s '.' > linter-errors.json
- uses: actions/ai-inference@a380166897b5408b8fb7dddd148142794cb5624a # 2.0.6
id: ai-linter-analysis
if: failure()
with:
model: mistral-ai/Ministral-3B
input: |
diff: ${{ steps.git-diff.outputs.raw-diff }}
prompt-file: ./linter-errors.json
system-prompt: |
You are an expert software engineer who specializes in diagnosing and fixing software build and runtime failures. Always provide structured reasoning and propose concrete fixes when possible.
Task: Analyze the logs of the super-linter-output/ folder from the failed `ubuntu-latest` CI workflow run. Cross-reference the errors with the code diff to determine the root cause of the failure.
{{ diff }}
Objectives:
1. **Diagnosis:** Identify patterns, anomalies, or dependencies that could explain the failure. What is the most probable root cause?
2. **Reasoning:** Explain why this root cause is plausible — referencing specific log lines, timestamps, or stack traces.
3. **Resolution:** If a fix is evident, describe your reasoning process and propose an exact code or configuration change. Present your solution as a unified diff (diff format).
4. **Reflection:** If no clear fix is identifiable, summarize which parts of the log are ambiguous and what further information would be needed to proceed.
Goal: Deliver an insightful and technically sound explanation that not only solves the issue but also strengthens understanding of the system's behavior and failure patterns.
- uses: jayqi/failed-build-issue-action@1a893bbf43ef1c2a8705e2b115cd4f0fe3c5649b # 1.2.0
if: failure()
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
title-template: "Super-linter has failed"
create-label: false
body-template: |
The linter step has failed. Please check for new major versions and update manually.
Please check the [logs](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}) for more details.
## AI Analysis of Linter Failures
${{ steps.ai-linter-analysis.outputs.response }}
check-tox:
name: Check syntax (tox)
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # 6.0.2
with:
persist-credentials: false
- name: Install tox
run: pip install tox
- name: Run tox lint validation
run: tox -e lint
- name: Run tox documents validation
run: tox -e docs