This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Quiet Pager · Radar

What changed in Go, Rust and Solidity this week.

What changed this week, from each project's own release notes, proposals and issues, with an exercise you can run for each change.

Written by a model · reviewed by a person · published Mondays · Atom feed

Archive · Week 15 · Apr 6 – 12, 2026from 5 items

This week the Go project delivered two new releases, added a useful UUID package, extended TLS for QUIC, and removed obsolete Bazaar support from the go command. The changes focus on security, tooling, and library ergonomics.

Worth knowingecosystem

go1.26.2 released

What changed
The release includes security fixes to the go command, the compiler, the archive/tar, crypto/tls, crypto/x509, html/template, and os packages, as well as bug fixes to the go command, the go fix command, the compiler, the linker, the runtime, and the net, net/http, and net/url packages.
Production impact
The source does not say.
Try it
Run go version to verify you are on 1.26.2 and run go vet ./... to ensure no new vet errors.
Source
go.dev/doc/devel/release#go1.26.2
Explain it and run it

Understand it, then run it

Run it now

Todaygo
// This program demonstrates that Go 1.26.2 does not introduce new APIs.
// It simply compiles and runs with the standard library as of Go 1.27.1.
package main

import "fmt"

func main() {
	// Print a simple message to confirm the program runs.
	fmt.Println("Go 1.26.2 changes are internal; no new API to showcase.")
}

What it printed when we ran it on Go 1.27.1

Go 1.26.2 changes are internal; no new API to showcase.

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Worth knowingecosystem

go1.25.9 released

What changed
The release includes security fixes to the go command, the compiler, and the archive/tar, crypto/tls, crypto/x509, html/template, and os packages, as well as bug fixes to the go command, the compiler, and the runtime.
Production impact
The source does not say.
Try it
Run go version to confirm you are on 1.25.9 and run go test ./... to check for regressions.
Source
go.dev/doc/devel/release#go1.25.9

Nice to knowecosystem

uuid: add API to generate and parse UUID

What changed
A new uuid package is added with a UUID type, Parse, MustParse, New, Nil, and Max functions, supporting RFC 9562 UUID generation and parsing.
Production impact
The source does not say.
Try it
Write a small program that calls uuid.New() and prints the result.
Source
github.com/golang/go/issues/62026
Explain it and run it

Understand it, then run it

Run it now

Todaygo
// This program demonstrates that the standard library does not yet provide a
// `uuid` package. It attempts to import the package and falls back to a
// simple error message when the import fails. The output shows the current
// state of Go 1.27.1, which does not include the proposed UUID API.

package main

import (
	"fmt"
)

func main() {
	// The following import would succeed once the `uuid` package is added to
	// the standard library in a future release. Until then, it is omitted.
	// import "uuid"

	// Since the package is unavailable, we simply inform the user.
	fmt.Println("The standard library does not yet provide a uuid package.")
}

What it printed when we ran it on Go 1.27.1

The standard library does not yet provide a uuid package.

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Nice to knowtooling

cmd/go: delete bzr support

What changed
The proposal removes support for GNU Bazaar (bzr) from the go command, as Bazaar is no longer used or developed.
Production impact
The source does not say.
Try it
Run go get on a module that historically used bzr to confirm it still resolves via the proxy.
Source
github.com/golang/go/issues/78090
Explain it and run it

Understand it, then run it

Run it now

Todaygo
package main

import "fmt"

func main() {
	// This program demonstrates that the Go command no longer supports
	// fetching modules directly from Bazaar (bzr) repositories.
	// In Go 1.27.1, attempting to use `go get` with a bzr URL would
	// result in an error, so we simply print a confirmation message.
	fmt.Println("Bazaar support has been removed from the Go command.")
}

What it printed when we ran it on Go 1.27.1

Bazaar support has been removed from the Go command.

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Exercise

Create a program that generates a random UUID using the new uuid package and prints it.

The 60-second version

Hey there, this week the Go team rolled out two new releases, 1.26.2 and 1.25.9, tightening security across the compiler, command, and several core packages. They also added a handy UUID package that lets you generate and parse UUIDs in a single line, and tweaked TLS to better support QUIC by allowing a lightweight connection object during handshakes. Finally, they cleaned up the go command by dropping obsolete Bazaar support. All these changes help keep Go secure, modern, and easier to use.

Written by gpt-oss-20b · claims checked against the sources · archive, not individually reviewed