Skip to content

v1.11.0 - #201

Merged
BakerNet merged 1 commit into
mainfrom
post/v1.11.0
Sep 3, 2026
Merged

BakerNet merged 1 commit into
mainfrom
post/v1.11.0

Conversation

@BakerNet

@BakerNet BakerNet commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Related PR(s)

Related Issue(s)

Summary / Background

@BakerNet
BakerNet merged commit 24863a0 into main Sep 3, 2026
6 of 7 checks passed
@BakerNet
BakerNet deleted the post/v1.11.0 branch September 3, 2026 00:57

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request updates the version of the codeowners-plus GitHub Action in the README.md file from v1.9.1 to v1.11.0, and increments the CLI tool version in tools/cli/main.go from v1.9.2.dev to v1.11.1.dev. There are no review comments, and I have no feedback to provide.

@github-actions
github-actions Bot requested a review from zbedforrest September 3, 2026 00:58
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Codeowners approval required for this PR:

@greptile-apps

greptile-apps Bot commented Sep 3, 2026

Copy link
Copy Markdown

Confidence Score: 5/5

The PR appears safe to merge because both version updates are consistent with the repository’s release lifecycle.

The README points to the intended v1.11.0 Action tag, while the CLI’s v1.11.1.dev value matches the post-release script’s next-patch development convention.

Important Files Changed

Filename Overview
README.md Updates the example Action reference to the internally aligned v1.11.0 release tag; no actionable defect was established.
tools/cli/main.go Advances the embedded CLI version to the expected post-v1.11.0 development version, matching the release automation.

Reviews (1): Last reviewed commit: "v1.11.0" | Re-trigger Greptile

asyncawaitpromise added a commit that referenced this pull request Sep 3, 2026
main gained GitHub Enterprise support (#199) and the v1.11.0 release (#201)
while this branch was open.

Resolved:
- README coverage badge: regenerated from the merged tree; covbadge.yml fails
  CI on a stale number, so neither side's value would have done.
asyncawaitpromise added a commit that referenced this pull request Sep 3, 2026
main gained GitHub Enterprise support (#199) and the v1.11.0 release (#201)
while this branch was open.

Resolved:
- README coverage badge: regenerated from the merged tree; covbadge.yml fails
  CI on a stale number, so neither side's value would have done.
asyncawaitpromise added a commit that referenced this pull request Sep 3, 2026
main gained GitHub Enterprise support (#199) and the v1.11.0 release (#201)
while this branch was open.

Resolved:
- README coverage badge: regenerated from the merged tree; covbadge.yml fails
  CI on a stale number, so neither side's value would have done.
- orphaned_approval_test.go: gh.NewClient took a fourth argument in #199. This
  branch adds a caller main never saw, so it merged clean and broke the build.
asyncawaitpromise added a commit that referenced this pull request Sep 3, 2026
main gained GitHub Enterprise support (#199) and the v1.11.0 release (#201)
while this branch was open.

Resolved:
- README coverage badge: regenerated from the merged tree; covbadge.yml fails
  CI on a stale number, so neither side's value would have done.
- main.go Flags: kept both ApiUrl (#199) and HunkFilter (this branch); the
  conflict was gofmt realignment, not a real collision.
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