Those checks were *very likely* meant to clamp the max value,
not the min one.

Fixes https://github.com/godotengine/godot/issues/10059#issuecomment-606993001.

Add missing docs for assert message in GDScript

Fix for Vulkan loader build error caused by incomplete alias

Seems like this was overlooked in PR #31142. See also issue #17082.

Add a method to retrieve active material from MeshInstance

Fixes #37465. The #37369 commit which added an alias for linuxbsd
platform did not work with the latest branch.

Register SubViewport class

[master] Mono/C#: Add iOS support

Fix more -Wmaybe-uninitialized warnings with target=release_debug

I have no idea why those don't get triggered in target=debug builds.

Fixes #37461.

doc: Sync classref with DisplayServer/Window changes

Also ignore new Android build artifact.

Right now, games only work on devices when exported with FullAOT+Interpreter.
There are some issues left that need to addressed for FullAOT alone. Right now,
it's giving issues with the Godot.NativeCalls static constructor.

MinGW should support both its own format `.a` and MSVC's format `.lib`,
but Mono's module was only using the former. With this change it's now
possible to build with MinGW and link the official Mono for Windows
which is built with MSVC.

Clarify docs for Thread.start() godotengine#36032

* Updated docs for Thread.start() to specify that the method argument
must accept one parameter.

Fixed errors in makerst pre-commit hook

Pre-commit hook instructions on Windows

doc: Update classref with node renames

SCons: Treat all warnings as errors

Move glow upscale quality to a global setting, for consistency

After an effort spanning several years, we should now be warning-free
on all major compilers, so we can set `-Werror` to ensure that we don't
introduce warnings in new code.

Disable -Werror=strict-overflow on GCC 7 though, as it seems bogus and
was fixed in 8+.

And simplify code in CSGShape.

A few extra renames for classes which were missed in last week's PRs.

SCons: Format buildsystem files with psf/black

Also install and use pygmentize to visualize clang-format and black
diffs.

Configured for a max line length of 120 characters.

psf/black is very opinionated and purposely doesn't leave much room for
configuration. The output is mostly OK so that should be fine for us,
but some things worth noting:

- Manually wrapped strings will be reflowed, so by using a line length
  of 120 for the sake of preserving readability for our long command
  calls, it also means that some manually wrapped strings are back on
  the same line and should be manually merged again.

- Code generators using string concatenation extensively look awful,
  since black puts each operand on a single line. We need to refactor
  these generators to use more pythonic string formatting, for which
  many options are available (`%`, `format` or f-strings).

- CI checks and a pre-commit hook will be added to ensure that future
  buildsystem changes are well-formatted.

Properly handle node remove via undo

Prevent shader crash if multiple variables has been declared in 'for'

Alias `platform=x11` to `platform=linuxbsd` in SCons