Skip to content

chore: prepare 7.3.2 release - #191

Merged
soulteary merged 1 commit into
mainfrom
release/7.3.2
Oct 11, 2026
Merged

soulteary merged 1 commit into
mainfrom
release/7.3.2

Conversation

@soulteary

Copy link
Copy Markdown
Owner

Prepare 7.3.2 for the requested maintenance release. Synchronize the release version, current deployment examples and documentation; preserve historical release notes.

The release includes the merged Go 1.27.2 and dependency upgrades.

Validation: version/documentation consistency checks and repository CI must pass before tagging.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-11T13:53:55.559544Z 63f475f PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 63f475fe9e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

If GoReleaser started and any versioned release asset or image exists, do not
delete the tag and reuse the version. Preserve the evidence, fix the cause on
`main`, and publish the next patch version (for example, 7.3.1). This avoids
`main`, and publish the next patch version (for example, 7.3.2). This avoids

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use 7.3.3 as the next patch example

When a 7.3.2 publish has already produced immutable artifacts, 7.3.2 is precisely the version this paragraph says not to reuse, so identifying it as the next patch could lead an operator into a duplicate-tag or artifact collision. Use 7.3.3 here and in the mirrored Chinese release guide.

Useful? React with 👍 / 👎.

@soulteary
soulteary merged commit dcbec55 into main Oct 11, 2026
11 checks passed
@soulteary
soulteary deleted the release/7.3.2 branch October 11, 2026 13:58
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