various: Bump Go ports for Go 1.26.10 / 1.27.3d81b7ba3c3
Port details
net/exoscale-cli1.93.0_10
Manage your Exoscale infrastructure easily from the command-line
- Maintainer
- egypcio@FreeBSD.org
- Packages
- exoscale-cli 1.93.0_10
- Upstream
- Higher version available: 1.103.2
- CPE
- none, CVEs only via VuXML
- WWW
- https://github.com/exoscale/cli
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (18)
various: Bump Go ports031fc6bfbf
many: Bump go ports for 1.26.8 and 1.27.1dd0905142a
various: Bump go ports for go-1.25.14 / 1.26.74867821cd6
various: Bump go ports for go-1.25.13 / 1.26.66d39dcf04e
various: Bump go ports for go-1.25.12 / 1.26.54ea3547132
various: Bump go ports for go-1.25.11 / go-1.26.4dd8dc2a59d
various: Bump ports for Go 1.25.104e243a83f8
various: Bump go ports for go-1.25.9 / 1.26.27507e72a84
various: Bump ports for Go 1.25.8a8d318da7c
net/exoscale-cli: update 1.84.0 to 1.93.010e473c6e4
various: Bump ports for Go default 1.24->1.2597685c1886
various: Bump Go ports for 1.24.13529df949a5
various: Bump Go ports for 1.24.12013f2d30b0
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.75d873b56a
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,modulesf45b1d07f5
go123 ports: Bump for 1.23.12b6703954e3
[NEW] net/exoscale-cli: Manage your Exoscale infrastructure from the cli Command-line tool for everything at Exoscale: compute, storage, dns. WWW: https://github.com/exoscale/cli24a7c69a24