|
Number of commits found: 6
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.2.1_3
11 Feb 2026 19:21:45
     |
Adam Weinberger (adamw)  |
various: Bump ports for Go default 1.24->1.25 |
0.2.1_2
05 Feb 2026 16:48:00
|
Adam Weinberger (adamw) |
various: Bump Go ports for 1.24.13 |
0.2.1_1
16 Jan 2026 17:49:03
|
Adam Weinberger (adamw) |
various: Bump Go ports for 1.24.12 |
0.2.1
15 Dec 2025 23:06:00
|
Dag-Erling Smørgrav (des) |
many: Unpin Go ports
* Ports that were pinned to a deprecated version of Go (1.23 or older)
have been unpinned.
* Ports that were pinned to a still-supported version of Go (1.24 or
newer) have been converted to requesting that as their minimum Go
version.
* Ports that had been forcibly deprecated for pinning an expired Go
version have been undeprecated. |
0.2.1
05 Dec 2025 14:07:28
|
Adam Weinberger (adamw) |
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 (Only the first 15 lines of the commit message are shown above  ) |
0.2.1
17 Oct 2025 03:54:47
|
Gabriel M. Dutra (dutra) |
sysutils/gonzo: Add new port
A powerful, real-time log analysis terminal UI inspired by k9s.
Analyze log streams with beautiful charts, AI-powered insights,
and advanced filtering - all from your terminal. |
Number of commits found: 6
|
As an Amazon Associate I earn from qualifying purchases.
