release: 1.7.2

[openai-sdks]

Automated Release PR

1.7.2 (2026-08-11)

Chores

• api: Update generated-source attribution in file headers (1b6ec73)
• api: Update generated-source attribution in file headers (#49) (1b6ec73)

---

This PR was generated with Release Please. See documentation.

[jbeckwith-oai]

CHANGELOG.md lists the only 1.7.2 change twice: both bullets have the same description and point to the same 1b6ec73 commit, with the second merely adding the #49 link. This duplicate will flow directly into the published GitHub release notes. Please collapse these into one entry (preferably the PR-linked form), and fix the release metadata/regeneration input if needed so Release Please does not reintroduce it.

[jbeckwith-oai]

The release-note duplication is still present on this regenerated head: both 1.7.2 bullets describe the same change and point to the same 1b6ec73 commit, with the second only adding the #49 link. Publishing this release would therefore duplicate the sole change in the GitHub release notes. Please collapse these into one PR-linked entry and fix the Release Please input/history if necessary so regeneration keeps it deduplicated. CI is green; this remains the only blocker.

[jbeckwith-oai]

The release-note blocker remains: the 1.7.2 changelog lists the sole 1b6ec73 change twice. Both bullets describe the same generated-source attribution update and point to the same commit; the second merely adds the #49 link. This will duplicate the only change in the published release notes. Please collapse these into one PR-linked bullet and fix or regenerate the Release Please source so the entry stays deduplicated. The version metadata, full v1.7.1 release delta, formatting, vet, build, diff hygiene, and file-size thresholds otherwise look clean; exact-head GitHub test, lint, and analysis checks are green (build-artifacts was still running at review time).