[dependabot]

Bumps https://github.com/atelico/gdstyle from v0.3.1 to 0.3.3.

Release notes

Sourced from https://github.com/atelico/gdstyle's releases.

v0.3.3

gdstyle 0.3.3

A formatter fix release for files that use @warning_ignore_start and @warning_ignore_restore. fmt no longer changes which code a region covers, and it keeps the two markers tight against the region.

Fixed

• fmt no longer moves members into or out of a @warning_ignore_start region. The two markers are standalone lines, and the reorder moved each one with whichever member followed it, so the pair did not move together:

  var health = 10
  @warning_ignore_start("unused_signal")
  signal a
  signal b
  @warning_ignore_restore("unused_signal")
  var z = 1

  0.3.2 sorted the signals above health and left the restore marker with z, so health ended up inside the region with its warnings silenced:

  @warning_ignore_start("unused_signal")
  signal a
  signal b
  var health = 10
  @​warning_ignore_restore("unused_signal")
  var z = 1

  fmt now skips the reorder whenever it would change which lines a region covers, in the script and in inner classes. It still reorders when only members outside the region move. On a skipped file check keeps reporting order/class-member-order, so the order can be fixed by hand. The README has a new section, "When the formatter leaves the order alone", that lists the cases. (#41)

• Region markers stay tight against the code they bracket. The gap between members could land between @warning_ignore_start(...) and the first member it covers. The start marker now counts as the head of the first covered member (above its doc and comment block, if it has one), the restore marker as the tail of the last one, and blank lines between a marker and its region

... (truncated)

Changelog

Sourced from https://github.com/atelico/gdstyle's changelog.

0.3.3 (2026-10-11)

• Fixed: fmt no longer changes which members a @warning_ignore_start / @warning_ignore_restore region covers when it reorders (#41).
• Fixed: fmt keeps region markers tight against the region, with blank lines outside it (#41).

0.3.2 (2026-10-11)

• Added: blank_line_between_public_and_private config setting, off by default (#38, #39).
• Fixed: fmt no longer separates a standalone @warning_ignore(...) line from its declaration (#40).

Commits

• 8b510f2 chore(release): 0.3.3
• 8205384 fix(formatter): keep @​warning_ignore_start regions intact when reordering and...
• 2c04926 chore(release): 0.3.2
• 6dc903b fix(formatter): keep standalone @​warning_ignore attached to its declaration (...
• 092f2e2 feat(formatter): add opt-in blank line between public and private vars (#39)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)