net-mgmt/check_syncthing 1.0.0_13

various: Bump Go ports for Go 1.26.10 / 1.27.3

various: Bump Go ports

many: Bump go ports for 1.26.8 and 1.27.1

various: Bump go ports for go-1.25.14 / 1.26.7

various: Bump go ports for go-1.25.13 / 1.26.6

various: Bump go ports for go-1.25.12 / 1.26.5

various: Bump go ports for go-1.25.11 / go-1.26.4

various: Bump ports for Go 1.25.10

various: Bump go ports for go-1.25.9 / 1.26.2

various: Bump ports for Go 1.25.8

various: Bump ports for Go default 1.24->1.25

various: Bump Go ports for 1.24.13

various: Bump Go ports for 1.24.12

net-mgmt/check_syncthing: Update 0.0.6 => 1.0.0, undeprecate

Changelog:
https://github.com/dsh2dsh/check_syncthing/releases/tag/v1.0.0

PR:	291433

many: Unsupported Go dep; deprecate and schedule for removal

There are about 75 ports that depend on old, unsupported Go
versions. I've scheduled those Go versions for deletions on
2025/01/01, and so these ports are scheduled for removal on
that same day.

HOWEVER....

Likely NONE or VERY VERY FEW of these ports will actually need
to be deleted! This stems from a misunderstanding:

When go.mod says "go 1.23", it means that it requires AT LEAST
go-1.23. Locking a port to a specific go version should almost
never happen; it is reserved for when a package absolutely
cannot build with any newer version, and it almost means that
the port will only last 1 year (Go releases new minors twice a
year).

Where a port has
USES=go:1.23
maintainers should attempt build with just
USES=go

If that works, please either commit it or submit it in a PR.

Same goes go
USES=go:1.23,modules
to attempt
USES=go,modules

go: Bump ports for go124 update

Bump all go ports for yesterday's releases

all: Bump after lang/go122 update

PR:		284181
MFH:		2025Q1

Add net-mgmt/check_syncthing: Icinga2 monitoring plugin for syncthing daemon

PR:		279859