ci.yaml: enable-email-notifications: true

Add enable-email-notifications: true. This seems to be needed for sending information about failed runs. Apparently it doesn't make it difference if I add it to ci/workflows/.github/workflows/test-packaging.yaml.
Signed-off-by: Jan Lindemann <jan@janware.com>
standard-tests.yaml: Rename to ci.yaml
2026-06-08 19:14:00 +02:00 · 2026-06-08 19:13:59 +02:00 · 2026-06-08 18:46:30 +02:00
2 changed files with 5 additions and 4 deletions
--- a/.github/workflows/standard-tests.yaml
+++ b/.github/workflows/standard-tests.yaml
@ -1,4 +1,4 @@
-name: Standard CI tests
+name: CI
 on:
  pull_request:
    types: [opened, synchronize, reopened]
@ -7,7 +7,8 @@ on:
      - master
      - main
      - released
 enable-email-notifications: true
 jobs:
  CI:
-    name: Packaging test - All supported platforms
+    name: Packaging test
-    uses: ci/workflows/.github/workflows/test-packaging.yaml@master
+    uses: ci/workflows/.github/workflows/test-packaging.yaml@master-test
--- a/make/project.conf
+++ b/make/project.conf
@ -36,7 +36,7 @@ build = realpath
 [pkg.requires.suse]
 run = python3
-release = rpmbuild, python3-base, python3-pyright
+release = rpmbuild, python3-base
 [pkg.requires.debian]
 run = python3
Author	SHA1	Message	Date
Jan Lindemann	00af6a2b37	ci.yaml: enable-email-notifications: true All checks were successful CI / Packaging - Kali Linux (pull_request) Successful in 3m21s Details CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m22s Details CI / Packaging test (pull_request) Successful in 0s Details CI / Packaging - Kali Linux (push) Successful in 3m17s Details CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m15s Details CI / Packaging test (push) Successful in 0s Details Add enable-email-notifications: true. This seems to be needed for sending information about failed runs. Apparently it doesn't make it difference if I add it to ci/workflows/.github/workflows/test-packaging.yaml. Signed-off-by: Jan Lindemann <jan@janware.com>	2026-06-08 19:14:00 +02:00
Jan Lindemann	ace0e915ec	standard-tests.yaml: Rename to ci.yaml In another attempt at making CI workflow naming more concise: - Rename standard-tests.yaml to ci.yaml Currently the contents of this file covers everything CI-related that happens in the context workflows, so for the time being, naming it ci.yaml is just fitting. And it's going to be shorter in commit message summaries. Should a real need arise, we can always split the file up again. - Shorten names again, otherwise they don't fit into Forgejo's check-mark-popup. That should be self-explanatory in context: name: Default CI -> CI jobs.CI.name: Packaging test - All supported platforms -> Packaging test Signed-off-by: Jan Lindemann <jan@janware.com>	2026-06-08 19:13:59 +02:00
Jan Lindemann	8d174f03bd	project.conf: pkg.requires.suse.release -= python3-pyright All checks were successful Standard CI tests / Packaging - Kali Linux (pull_request) Successful in 3m17s Details Standard CI tests / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m35s Details Standard CI tests / Packaging test - All supported platforms (pull_request) Successful in 0s Details Standard CI tests / Packaging - Kali Linux (push) Successful in 3m18s Details Standard CI tests / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m19s Details Standard CI tests / Packaging test - All supported platforms (push) Successful in 0s Details Running pyright in a minimal docker container gives this error: $ pyright /usr/bin/npm-default: No such file or directory Traceback (most recent call last): File "/usr/bin/pyright-3.13", line 6, in <module> sys.exit(entrypoint()) ~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/pyright/cli.py", line 31, in entrypoint sys.exit(main(sys.argv[1:])) ~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/pyright/cli.py", line 18, in main return run(args, kwargs).returncode ~~~^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/pyright/cli.py", line 22, in run pkg_dir = install_pyright(args, quiet=None) File "/usr/lib/python3.13/site-packages/pyright/_utils.py", line 69, in install_pyright node.run( ~~~~~~~~^ 'npm', ^^^^^^ ...<5 lines>... stderr=subprocess.PIPE if silent else sys.stderr, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3.13/site-packages/pyright/node.py", line 144, in run subprocess.run(node_args, *kwargs), ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['/usr/bin/npm', 'install', \ 'pyright@1.1.409']' returned non-zero exit status 255. This means that on openSUSE, python3-pyright tries to pull in packages from the NPM registry. This increases the CI supply chain attack surface inacceptably, so remove pyright from the release prerequisites. That should be enough to remove it from the prerequisites of target check as well and allow it to succeed. The pyright check machinery itself remains useful, so keep it in place for developers who install python3-pyright manually. Signed-off-by: Jan Lindemann <jan@janware.com>	2026-06-08 18:46:30 +02:00