v2.0.0 - #214
Merged
Merged
v2.0.0#214
Conversation
Contributor
|
Coverage after merging release/2.0.0 into main will be
Coverage Report
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
22 tasks
Contributor
🔦 Lighthouse Report
|
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The documentation currently presents conflicting behavior for --pick-team-auto (common-prefix-only vs. additional sibling combo clustering), which should be reconciled before merging a major-release cut.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Cuts the v2.0.0 major release for github-code-search by bumping the package version and publishing the accompanying release documentation (blog + changelog), aligning the project’s published release narrative with the already-merged v2 feature set.
Changes:
- Bump
package.jsonversion from1.12.0to2.0.0. - Add the v2.0.0 release blog post and a new “v2 series” section in the blog index.
- Update
CHANGELOG.mdto replace the pending v2 entry with the published blog post link.
| File | Description |
|---|---|
| package.json | Version bump to 2.0.0 for the major release cut. |
| docs/blog/release-v2-0-0.md | New v2.0.0 release post documenting highlights and breaking changes. |
| docs/blog/index.md | Adds a dedicated “v2 series” section linking to the v2.0.0 post. |
| CHANGELOG.md | Updates the v2.0.0 row to point to the published release blog post. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+44
to
+46
| ### `--pick-team-auto` — resolve ambiguous sections automatically | ||
|
|
||
| New flag: auto-resolves combined sections whose team names share a common prefix (e.g. `tribe-a + tribe-a-p1` → `tribe-a`), without an explicit `--pick-team`. It also clusters combos that share a recurring team across siblings even without a literal common prefix, and always defers to an explicit `--pick-team` for the same section. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Cuts the v2.0.0 major release, closing EPIC #125 — hierarchical
--group-by-team-prefixgrouping and everything shipped since v1.12.0:package.jsonversion to2.0.0.docs/blog/release-v2-0-0.mdcovering: hierarchical team-prefix grouping (nested chains, auto-nesting,--pick-teamat every level,--pick-team-auto,--exclude-team-prefixes, removal of--group-by-team-prefix-consolidate),GCS_DEFAULT_ORG, thegh auth tokenfallback, the TUI/CLI exit-delay fix, thepicocolorsremoval, and the Bun ≥1.4 requirement bump — plus an explicit Breaking changes section.## v2 seriessection todocs/blog/index.md.CHANGELOG.md: replaces thev2.0.0 (pending)row with the real blog post link — no_pending_rows left.Once merged, I'll tag
v2.0.0onmainto trigger the release CD pipeline, and close #125 (all 10 sub-issues are already closed; this PR completes the epic's remaining Definition of Done items).How did you verify your code works?
bun test(1024 passing),bun run lint,bun run format:check,bun run knip,bun run build.tsall green.bun run docs:buildsucceeds; confirmed the homepage version badge and its blog link auto-derive tov2.0.0/release-v2-0-0from the bumpedpackage.jsonversion.