chore(main): release instro-unstable 1.8.0

[nominal-bot]

🤖 I have created a release beep boop

1.8.0 (2026-08-31)

Features

• awg: add burst to Keysight 33521B driver (#405) (bc38a6b)
• awg: add sweep to Keysight 33521B driver (#410) (a55974c)
• awg: use bulk download for small LAN waveforms (#432) (bde7b1e)
• publish categorical instrument reads as Measurement (#445) (6ccce83)

---

This PR was generated with Release Please. See documentation.

[claude]

Claude finished @nominal-bot's task in 23s —— View job

---

Review: no findings

• Gather context (PR is a release-please auto-generated version bump)
• Review changed files
• Post final findings

This PR only contains release-please's automated output: bumping packages/instro-unstable from 1.7.0 → 1.8.0 in the manifest and pyproject.toml, and appending the changelog entry for #405 (already reviewed separately). No hand-written code, driver logic, or docs changes to evaluate against AGENTS.md conventions — nothing to flag.

[greptile-apps]

Greptile Summary

This release PR advances instro-unstable from 1.7.0 to 1.8.0 and documents the Keysight 33521B burst feature.

• Updates the Release Please manifest and Python package metadata to 1.8.0.
• Adds the generated 1.8.0 changelog entry.
• Leaves the workspace lockfile’s package version stale.

Confidence Score: 4/5

The PR appears safe to merge, although the stale instro-unstable version in uv.lock should be refreshed with this release.

The release metadata and changelog agree on version 1.8.0, with the only accepted concern being non-blocking lockfile metadata drift.

Files Needing Attention: packages/instro-unstable/pyproject.toml and uv.lock

Important Files Changed

Filename	Overview
.github/release-please-manifest.json	Updates the instro-unstable release version to 1.8.0 consistently with the package metadata.
packages/instro-unstable/CHANGELOG.md	Adds the generated 1.8.0 release entry for the Keysight AWG burst feature.
packages/instro-unstable/pyproject.toml	Bumps the distribution to 1.8.0, but the corresponding editable workspace entry in uv.lock remains at 1.5.0.

Prompt To Fix All With AI

### Issue 1
packages/instro-unstable/pyproject.toml:3
**Lockfile version remains stale**

This release advances `instro-unstable` to 1.8.0 while its editable workspace entry in `uv.lock` remains at 1.5.0, so lockfile-based inspection reports outdated package metadata and a later lockfile refresh produces an unrelated correction.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore(main): release instro-unstable 1.8..." | Re-trigger Greptile}

[nominal-bot]

🤖 Created releases:

• instro-unstable-v1.8.0

🌻