[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted debputy 0.1.66 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 10 Mar 2025 22:11:30 +0000
Source: debputy
Architecture: source
Version: 0.1.66
Distribution: unstable
Urgency: medium
Maintainer: Debputy Maintainers <debputy@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Changes:
 debputy (0.1.66) unstable; urgency=medium
 .
   * LSP/Lint:
     - Ensure `dh_assistant` is run from the current source package root.
       This could cause false positive and false negative diagnostics
       with the LSP mode (`debputy lint` was unaffected).
     - Properly detect unused debhelper config files under `full`
       integration.
     - Flag substvars as `macro` in the semantic tokens. Editors that use
       semantic tokens for highlighting can now highlight substvars distinctly
       from the surrounding text.
     - Emit comment tokens for comments inside unknown fields in the semantic
       token feature. For editors that use semantic tokens for syntax
       highlighting, these inline value comments are now properly highlighted.
     - Consider relations with arch or build profile restrictions as complex
       to reduce false positives (at the cost of false negative) for duplicated
       relations.
     - Do not consider hidden files as patches. This avoids triggering
       "Unused Patch" diagnostics for `debian/patches/series" for editor
       swap files that were hidden but did not match the previous known
       patterns.
     - Make severanl of the LSP features (diagnostics, semantic tokens, and
       inlay hints) asynchronous. These requests will no longer stall
       `debputy` until responded. This will make `debputy` seem more
       responsive on larger files like `linux` (its generated `d/control`
       is 0.5 MB).
       Note that other requests (completion, hover) are still synchronous
       and will block other requests (including ongoing asynchronous ones).
 .
   * debputy lsp server: Correctly track partial diagnostic reports
     internally. The previous version did not emit partial diagnostic
     reports, so this bug could not trigger any unintended behavio (
     but probably would have down the line).
Checksums-Sha1:
 6f3e0c1d406d54185d1430496fca09a8802f74c4 2180 debputy_0.1.66.dsc
 928319c339f779f315ce44336eab8f4cab015971 676816 debputy_0.1.66.tar.xz
Checksums-Sha256:
 64e08f7aa7f3003ab0ad572aa8706aa878c72b8e6fca8f7dfe5da01836e911fe 2180 debputy_0.1.66.dsc
 253423f7f50656beb76dacb44fac941af4904860db0d5087f86208b129807772 676816 debputy_0.1.66.tar.xz
Files:
 1ceab9045f24a28b6da4d95b9e483fc0 2180 devel optional debputy_0.1.66.dsc
 5579b60592e7385daa5c3b2aa8fdce01 676816 devel optional debputy_0.1.66.tar.xz

-----BEGIN PGP SIGNATURE-----

iQFGBAEBCgAwFiEE9ecZmu9eXGflVYc/dA1oiINl0okFAmfPZnkSHG5pZWxzQHRo
eWtpZXIubmV0AAoJEHQNaIiDZdKJ3hwIALdbGtuxP7/C2AcryE0ypZGwqFtbfANo
5zxYwHfQbCnz1aLtDstzc1eQDuiPQZXkc7SqKGxRCGP5z+bMObq2RxmGm9euXlHD
AVkrCH4EonYdWZypzNoy+pVNHbKl7EO4VijJurkGAPX2arH2CBv6n1vW0IQwxYyX
gqe00k/Cxw2Gi/De4o1km0fG7kB/8Hqb+HURvQaN+CIIxj3N3zdeZkGTShu/FKfm
7Ov687rPGMvOoDDIh2zEt/U2SqEyBv5n6uuICOw1P3/e5QlAVBxK+fVWiajkOeSr
xVqCf/0/hCg10eHYICGzwqHAvQPvWlcSUY1e6i8rMzzwG4goXjYLHjw=
=lzLU
-----END PGP SIGNATURE-----

Attachment: pgpGXx2ankkFi.pgp
Description: PGP signature


Reply to: