golang-stay-updatedlisted

# Research Current Go Information Current ecosystem facts expire quickly. Browse live sources, state the observation date, and distinguish released behavior from proposals or experiments. ## Start from the user's decision Identify whether the user needs: - the current stable or supported Go release; - changes between specific versions; - compatibility implications for a repository; - security advisories; - upcoming proposals or experiments; - authoritative learning and ongoing-update sources. If a repository is involved, inspect its go and toolchain directives, CI matrix, release policy, and dependencies. Do not assume the locally installed Go version is the project's target. ## Prefer official sources Use the smallest relevant set: - Go release history and version-specific release notes on go.dev; - the Go blog for official announcements and migration context; - go.dev/doc and package documentation for current language and tooling behavior; - vuln.go.dev for Go vulnerability records; - the Go proposal tracker and issue repository for proposals, clearly labeled as unreleased; - pkg.go.dev and canonical module repositories for library-specific facts. Community posts, conference talks, newsletters, forums, and social media can explain adoption experience but are secondary sources. Identify them as community perspective and verify technical claims against primary sources. Do not reproduce a static list of people, channels, or popular projects. Recommend a small monitor