Age | Commit message (Collapse) | Author |
|
(cherry picked from commit 4751890acbf3b98f93386649f2d393b5c4e3cf91)
|
|
Closes #6430
(cherry picked from commit 8023b8c8fe6cfb13e4a561c87177744612bb42f9)
|
|
See https://github.com/actions/setup-python/issues/207
pytest isn't ready yet:
https://github.com/pytest-dev/pytest/issues/8539
(cherry picked from commit 0c1414c6aaa419cba812b751c97c87e10cd6009e)
|
|
Too many false positives, and it seems impossible to ignore a single rule.
|
|
|
|
It requires some time and network access, so no need to run it as part of the automated tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unfortunately, GitHub won't let us clone asciidoc to ../asciidoc :(
|
|
|
|
Closes #6338
|
|
|
|
|
|
|
|
Closes #6298
|
|
This reverts commit 545e37b913f9db7efaff22074372ebba4c794986.
Doesn't actually seem to work...
|
|
|
|
https://github.com/Gottox/irc-message-action/issues/5 is fixed
|
|
|
|
That's what we use with the newer PyInstaller releases, too.
|
|
Needs a couple of follow-up commits for workarounds, which hopefully
aren't needed anymore at a later point.
Fixes #6068
|
|
See #5551
|
|
See https://github.com/actions/virtual-environments/issues/841
|
|
This makes sure we don't use a stale qute_pylint version in CI.
|
|
|
|
|
|
Follow-up to df7e0553d8bf3697c577b72ed4077ac90be07c74
|
|
We test Qt 5.15.2, but that's based on a newer Chromium version:
Qt 5.14.x -> Chromium 77
Qt 5.15.0 -> Chromium 80
Qt 5.15.2 -> Chromium 83
Some behavior changes between Chromium versions (see e.g. #5915), so it
makes sense to test both.
Picking 5.15.0 rather than .1 due to renderer process crashes in
5.15.1 (#5721). Doesn't matter much on the CI as we don't use WebRTC,
but if someone wants to downgrade with mkvenv.py for some reason, .0
will be more useful than .1.
|
|
This reverts commit 7c1f177572daeb2063ab58b5669a4c3c02df6235.
Worked on dev, now broken on master?
|
|
|
|
|
|
|
|
|
|
See #5663 and #5896 (which we don't test for at the moment)
|
|
This reverts commit 74ad8fd545f72c76a55dcd2d87683041a09816cb.
|
|
|
|
It emits a setup warning because of a missing Python 2 pip otherwise:
https://github.com/github/codeql-action/pull/316
|
|
There currently are warnings about ubuntu-latest soon being 20.04 rather
than 18.04. For those environments, we don't actually care about the
underlying OS (linters/codeql/irc should work no matter what), but it's
still good to be explicit about the OS choice. This avoids the warnings
and makes things more predictable. Also, updating it once every 2
years (for Ubuntu LTS releases) shouldn't be a big issue.
|
|
|
|
|
|
|
|
See #4800
|
|
- It only seems to catch some dependencies, not all
- Its PRs (without batching) are kind of noisy
- Despite the GitHub docs saying otherwise, it seems to open PRs for
forks...
- GitHub Actions seem to use semantic versioning pretty much
consistently, so this should hopefully work out without explicit
pinning.
|
|
See https://github.com/actions/toolkit/security/advisories/GHSA-mfwh-5m23-j46w
|
|
Bumps [actions/setup-python](https://github.com/actions/setup-python) from v2.1.2 to v2.1.3.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v2.1.2...c181ffa198a1248f902bc2f7965d2f9a36c2d7f6)
Signed-off-by: dependabot[bot] <support@github.com>
|