From 1a56efb25ab72ce9af9139086fa479e9e2cc9d15 Mon Sep 17 00:00:00 2001 From: Jan Lindemann Date: Mon, 8 Jun 2026 14:27:42 +0200 Subject: [PATCH 1/5] 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 --- .github/workflows/{standard-tests.yaml => ci.yaml} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename .github/workflows/{standard-tests.yaml => ci.yaml} (72%) diff --git a/.github/workflows/standard-tests.yaml b/.github/workflows/ci.yaml similarity index 72% rename from .github/workflows/standard-tests.yaml rename to .github/workflows/ci.yaml index 80b6f313..2689a374 100644 --- a/.github/workflows/standard-tests.yaml +++ b/.github/workflows/ci.yaml @@ -1,4 +1,4 @@ -name: Standard CI tests +name: CI on: pull_request: types: [opened, synchronize, reopened] @@ -9,5 +9,5 @@ on: - released jobs: CI: - name: Packaging test - All supported platforms - uses: ci/workflows/.github/workflows/test-packaging.yaml@master + name: Packaging test + uses: ci/workflows/.github/workflows/test-packaging.yaml@master-test From 9e4b216ef0bff524789210c64f38aafe663fea69 Mon Sep 17 00:00:00 2001 From: Jan Lindemann Date: Mon, 8 Jun 2026 14:55:04 +0200 Subject: [PATCH 2/5] 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 --- .github/workflows/ci.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 2689a374..6d35e3c8 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -7,6 +7,7 @@ on: - master - main - released +enable-email-notifications: true jobs: CI: name: Packaging test From 8d174f03bd222a61cf93c2e7c22cffb463406dc0 Mon Sep 17 00:00:00 2001 From: Jan Lindemann Date: Mon, 8 Jun 2026 15:55:24 +0200 Subject: [PATCH 3/5] project.conf: pkg.requires.suse.release -= python3-pyright 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 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 --- make/project.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/make/project.conf b/make/project.conf index b9231d0c..9641d6d5 100644 --- 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 From ace0e915eccec37512f7a50346a5c39af7d86ba0 Mon Sep 17 00:00:00 2001 From: Jan Lindemann Date: Mon, 8 Jun 2026 14:27:42 +0200 Subject: [PATCH 4/5] 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 --- .github/workflows/{standard-tests.yaml => ci.yaml} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename .github/workflows/{standard-tests.yaml => ci.yaml} (72%) diff --git a/.github/workflows/standard-tests.yaml b/.github/workflows/ci.yaml similarity index 72% rename from .github/workflows/standard-tests.yaml rename to .github/workflows/ci.yaml index 80b6f313..2689a374 100644 --- a/.github/workflows/standard-tests.yaml +++ b/.github/workflows/ci.yaml @@ -1,4 +1,4 @@ -name: Standard CI tests +name: CI on: pull_request: types: [opened, synchronize, reopened] @@ -9,5 +9,5 @@ on: - released jobs: CI: - name: Packaging test - All supported platforms - uses: ci/workflows/.github/workflows/test-packaging.yaml@master + name: Packaging test + uses: ci/workflows/.github/workflows/test-packaging.yaml@master-test From 00af6a2b37257a50436d2069e1bedd21322a1d51 Mon Sep 17 00:00:00 2001 From: Jan Lindemann Date: Mon, 8 Jun 2026 14:55:04 +0200 Subject: [PATCH 5/5] 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 --- .github/workflows/ci.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 2689a374..6d35e3c8 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -7,6 +7,7 @@ on: - master - main - released +enable-email-notifications: true jobs: CI: name: Packaging test