bc72687d7d
Update changelog URLs
2025-12-08 16:55:52 +01:00
c32b7d4b60
Fix dependency update issues
2025-12-08 10:53:13 +01:00
f2547f8a09
scripts: Make smoke test fail output less confusing
2025-11-30 18:46:03 +01:00
17c19a09b7
build_release: Try to get more information on crashes
...
Currently CI crashes on macOS, but without any useful logs.
2025-11-30 18:11:25 +01:00
9316d428ef
ci: Drop Archlinux Qt 5 images/jobs
...
For now, Qt 5 is still tested via the Qt 5.15 PyPI wheels.
See https://github.com/qutebrowser/qutebrowser/issues/8417#issuecomment-3495979318
https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/U45C4RAW4IXVLO376XGFNLEGGFFXCULV/
2025-11-11 09:13:30 +01:00
3fce0518bd
scripts: Avoid showing entire file tree diff in CI log
2025-10-24 17:00:19 +02:00
0c2a673e27
scripts: Clean up build_release
2025-10-24 15:06:20 +02:00
afa456f396
ci: Skip existing artifacts when reuploading
...
After a release failed and we want to retry,
some assets might already have been uploaded.
Skip those instead of attempting to reupload.
2025-10-24 14:53:40 +02:00
461077b6cf
ci: Fix reupload in script
2025-10-24 14:34:20 +02:00
e208f5e121
ci: Add ability to reupload after borked release
2025-10-24 14:33:24 +02:00
0f320051e0
scripts: Ignore another line during smoke tests
2025-10-24 14:17:29 +02:00
da9bd515fd
scripts: Update build-release ignores for Qt 6.10
2025-10-24 12:05:35 +02:00
e300327eea
Update certifi changelog URL
2025-10-10 19:03:14 +02:00
78b55f84cc
scripts: Handle ImportError without QUTE_QT_WRAPPER set in link_pyqt
...
If link_pyqt() is run from mkvenv.py, QUTE_QT_WRAPPER may not be set,
so we shouldn't crash when trying to display import error messages.
2025-09-05 11:24:51 +02:00
22f1b57347
lint: Move check-manifest into pyroma
...
pyroma now runs check-manifest if installed,
so we can simplify things there.
2025-07-07 08:09:47 +02:00
858606c18d
ci: Remove QtWebKit testing
...
It's broken in weird ways since recently (`:version` not loading,
segfault in test_version.py). Since nobody should be using it anyways,
there is no point in spending time on debugging a tricky issue.
Next step is probably ripping it out completely, but that's a separate
can of worms.
See #4039
2025-05-13 09:29:04 +02:00
81f65dbb46
docker: Install libxml2-legacy from official repos
...
Reverts:
- a3bdcca37b1b7557b73b06e79505889aef02e96cc5fe31e828
2025-05-08 09:21:35 +02:00
6cbf2847c8
docker: Try working around QtWebKit issues
2025-05-07 17:59:15 +02:00
102f43cbde
scripts: Ignore another stderr output on macOS
2025-05-06 14:08:00 +02:00
c5fe31e828
docker: Add link
2025-05-06 14:06:10 +02:00
9aef02e96c
docker: Don't install libxml2.13 for webkit
2025-05-06 10:28:17 +02:00
06e7950588
docker: Always install base-devel
2025-05-06 09:18:07 +02:00
1b7557b73b
docker: Don't run makepkg as root
2025-05-06 09:15:27 +02:00
5e6a878f64
docker: Also downgrade libarchive for QtWebEngine
2025-05-06 09:12:23 +02:00
a3bdcca37b
docker: Install libxml2.13
2025-05-06 09:11:20 +02:00
e67aea60e8
Update changelog link for mypy extensions
2025-04-25 16:50:07 +12:00
ef397e9417
Update changelog URLs
2025-03-31 08:40:01 +02:00
2f20e3b60b
Update iniconfig changelog url
2025-03-24 11:29:35 +01:00
237e90985d
docker: Downgrade libxslt
...
ImportError: /usr/lib/libxslt.so.1: undefined symbol: xmlCtxtParseDocument
2025-03-15 12:25:43 +01:00
4f985feede
update changelog URL
2025-03-10 23:05:00 +13:00
42c9973c01
update isort changelog link
2025-03-03 19:45:58 +13:00
eb2e39de1e
scripts: Add new bump-my-version deps
2025-02-17 10:55:22 +01:00
60f526d81f
Add new changelog URLs from bump-my-version
2025-02-03 18:40:35 +01:00
6b25fdf648
chore: replace bump2version with bump-my-version
2025-01-30 19:14:38 -07:00
322977dc0d
Update changelog URLs for twine upgrade
2025-01-27 16:15:28 +01:00
b3090870d3
scripts: Rename test_requirements function
...
Falsely flagged by https://github.com/m-burst/flake8-pytest-style/blob/master/docs/rules/PT028.md
2025-01-19 11:56:42 +01:00
7eb9bc45de
Adjust Pillow changelog URL
2025-01-06 15:05:02 +01:00
9e70ffeaad
Switch to legacy PDF.js build
...
The normal PDF.js build only officially supports the latest Chromium, so things
might break every once in a while with QtWebEngine (e.g. #8199 , #7335 ).
Let's instead bundle and recommend the legacy build.
Closes #8332
Closes #7721 (reworded)
Also see #7135
2024-12-10 11:47:39 +01:00
e7b346ecf2
scripts: Try harder to 'hdiutil create' the .dmg
...
See https://github.com/actions/runner-images/issues/7522#issuecomment-2527820259
2024-12-10 10:31:47 +01:00
8f274c4e18
mkvenv: Add arm64 to supported platforms
2024-12-10 00:47:04 +01:00
c501ae375e
scripts: Close sqlite connections properly in importer
...
Found thanks to runnning Python 3.13 tests on CI.
See #8205
2024-12-09 16:51:55 +01:00
4d5ed99ff5
link_pyqt: Try QtCore before sip
...
Makes for nicer error messages if there's no PyQt at all.
2024-12-09 13:59:33 +01:00
557cd19a1d
ci: Try harder to detach dmg image
...
See https://github.com/actions/runner-images/issues/7522
2024-12-06 21:45:27 +01:00
3a3c03a4df
In POSIX sh, echo flags are undefined
2024-12-06 19:40:28 +00:00
5cb14d4d4b
Run shellcheck over all scripts/*.sh files
...
See #8409
2024-12-06 20:39:34 +01:00
aed06c5f48
Add gherkin-official changelog URL
2024-12-05 19:26:58 +01:00
ffe7d00a62
Merge branch 'drop-py38'
2024-10-15 11:58:54 +02:00
cc3c1e2050
Enable pylint Too many positional arguments warning
...
This re-enables the pylint too-many-positional-arguments for the main
application code. It's still disabled for tests because that's how you pull in
pytlint fixtures, and I don't think we want to push people into being creative
with fixtures just to get around that.
When functions are called with many positional arguments the reader has to do
a bit of heavy lifting to figure out in what position a value is being passed,
and it's easier to make mistakes. So I would like to encourage using keyword
arguments for long argument lists.
I've set the `max-positional-arguments` to a completely arbitrary 7, from a
completely arbitrary 5, because there were many more violations under 7. If
like 99% of our functions fit under 7 it's probably fine.
Regarding the exceptions:
* objreg.register: I grepped it and it looks like everything is only passing
the first two args as positional already, lucky!
* `_get_color_percentage`: only one usage of it, but I was in "add directive
comment" mode
* update_3rdparty.py: only one usage, already using kwargs
* pyqtProperty: idk
* commands.py: "its complicated". Many methods in this file map to commands
used in qutebrowser's command mode. In that case it's usual for them to be
called as flags, rather than positional. But it could be complicated to wade
into that, and having one file excluded isn't so bad.
2024-10-15 11:55:04 +02:00
2ab963cef8
Remove pytz changelog URL
2024-10-15 11:55:04 +02:00
0fd6fc19f2
recompile_requirements: Fix with diff.mnemonicPrefix set
2024-10-15 11:55:04 +02:00
Florian Bruhin
toofar
Jun Chen
Ruben Gonzalez