Generate changelog for v0.2.0 (#258)

Author: karencfv

.github/ISSUE_TEMPLATE/release_checklist.md

@@ -14,7 +14,7 @@ labels: release
 - [ ] Make sure the [VERSION](https://github.com/oxidecomputer/oxide.go/blob/main/VERSION) and [oxide/version.go](https://github.com/oxidecomputer/oxide.go/blob/main/oxide/version.go) files have the new version you want to release.
 - [ ] Make sure the changelog file in the `.changelog/` directory is set to the new version you want to release.
 - [ ] Make sure all examples and docs reference the new version.
-- [ ] Generate changelog by running `make changelog` and add date of the release to the title.
+- [ ] Make sure you've pulled the latest tag on main, and generate changelog by running `make changelog`. Add the date of the release to the title, and update associated Oxide API version.
 - [ ] Release the new version by running `make tag`.
 - [ ] Update GitHub release description with release notes generated from `make changelog`.
 - [ ] Create a release branch from the commit of the release tag.

CHANGELOG.md

@@ -1,3 +1,18 @@
+# v0.2.0 (2025/Jan/07)
+
+Generated from Oxide API version [20241204.0.0](https://github.com/oxidecomputer/omicron/blob/rel/v12/rc1/openapi/nexus.json)
+
+### Notes
+
+This release is solely a version bump. Since pkg.go.dev does not recognise git tags with metadata suffixes,
+we are not able to set build metadata like the previous version. See associated [commit](https://go-review.googlesource.com/c/pkgsite/+/343631).
+
+### List of commits
+
+- [8357536](https://github.com/oxidecomputer/oxide.go/commit/8357536) Bump version for release v0.2.0 (#257)
+- [f314faf](https://github.com/oxidecomputer/oxide.go/commit/f314faf) release: bump to next version (#255)
+- [230e0cc](https://github.com/oxidecomputer/oxide.go/commit/230e0cc) release: v0.1.0+20241204.0.0 (#254)
+
 # v0.1.0+20241204.0.0 (2025/Jan/06)
 
 ### Breaking changes