Skip to content

chore: publish the 1.0.0 release - #1344

Merged
vdmkenny merged 1 commit into
mainfrom
codex/release-1.0
Nov 10, 2026
Merged

vdmkenny merged 1 commit into
mainfrom
codex/release-1.0

Conversation

@vdmkenny

Copy link
Copy Markdown
Collaborator

No changes have followed the first release candidate, so 1.0.0 ships as rc.1 built it. Remove the three prerelease settings from release-please's config, so it opens the release pull request for the final 1.0.0 rather than a second candidate, as docs/port/platform.md describes. Keep the Release-As line below in the squash commit.

Release-As: 1.0.0

No changes have followed the first release candidate, so 1.0.0 ships as rc.1 built it. Remove the three prerelease settings from release-please's config, so it opens the release pull request for the final 1.0.0 rather than a second candidate, as docs/port/platform.md describes. Keep the Release-As line below in the squash commit.

Release-As: 1.0.0
@vdmkenny
vdmkenny merged commit ece3666 into main Nov 10, 2026
4 checks passed
@vdmkenny
vdmkenny deleted the codex/release-1.0 branch November 10, 2026 11:22
vdmkenny pushed a commit that referenced this pull request Nov 10, 2026
🤖 I have created a release *beep* *boop*
---


##
[1.0.0](v1.0.0-rc.1...v1.0.0)
(2026-11-10)


### Chores

* publish the 1.0.0 release
([#1344](#1344))
([ece3666](ece3666))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant