-
-
Notifications
You must be signed in to change notification settings - Fork 4k
build(deps): bump github/super-linter from 5.0.0 to 6 #32609
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
build(deps): bump github/super-linter from 5.0.0 to 6 #32609
Conversation
Bumps [github/super-linter](https://github.com/github/super-linter) from 5.0.0 to 6. - [Release notes](https://github.com/github/super-linter/releases) - [Changelog](https://github.com/github/super-linter/blob/main/CHANGELOG.md) - [Commits](github/super-linter@45fc0d8...4e51915) --- updated-dependencies: - dependency-name: github/super-linter dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
2024-05-01 10:07:25 [FATAL] Failed to get [GITHUB_TOKEN]. Terminating because status reports were explicitly enabled, but GITHUB_TOKEN was not provided. Looks like (With |
cc @mrc0mmand |
The multi status feature requires $GITHUB_TOKEN, and since [0] it defaults to true. Since we don't need it, let's explicitly disable the feature. [0] super-linter/super-linter@e6e6e1f
ae767e9
to
b160ac9
Compare
Looks like since [0] the Super-Linter repo was moved to super-linter/super-linter and github/super-linter is just a fork, so let's update the reference accordingly. [0] github/super-linter@59fac79
Heh, this is a new one:
But this looks like an issue in the toolchain. |
What's weird is that to judge from https://github.com/systemd/systemd/actions/workflows/cifuzz.yml it doesn't always fail. Looking at google/oss-fuzz#11881 I'm guessing the toolchain was bumped recently and it could be it has something to do with that. It's hard to tell. |
Actually it always fails: https://github.com/systemd/systemd/actions/runs/8923406440/job/24507592361 but since it's already reproducible with the binaries from OSS-Fuzz The crash is reproducible on previous build. Code change (pr/commit) did not introduce crash so CIFuzz ignores it and bails out. The fuzz targets effectively aren't run though. |
google/oss-fuzz#11886 was closed so it should hopefully start working again once the new images are rolled out. |
Bumps github/super-linter from 5.0.0 to 6.
Release notes
Sourced from github/super-linter's releases.
Changelog
Sourced from github/super-linter's changelog.
... (truncated)
Commits
4e51915
Update README.md5336115
deps(dev-npm): bump@commitlint/config-conventional
in /dev-dependencies (#5521)a540e8d
deps(docker): bump dart from 3.3.3-sdk to 3.3.4-sdk (#5550)74733ba
deps(docker): bump hashicorp/terraform from 1.8.0 to 1.8.1 (#5551)1682dbc
deps(docker): bump alpine/terragrunt from 1.8.0 to 1.8.1 (#5552)90554b4
deps(github-actions): bump actions/download-artifact from 4.1.4 to 4.1.5 (#5553)46a0678
deps(github-actions): bump actions/upload-artifact from 4.3.1 to 4.3.2 (#5554)f33d4b2
deps(python): bump yq from 3.3.0 to 3.4.1 in /dependencies/python (#5555)72d4e76
deps(python): bump cfn-lint in /dependencies/python (#5556)0cbc4d9
deps(python): bump sqlfluff from 3.0.4 to 3.0.5 in /dependencies/python (#5557)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)