Skip to content

chore(release): 1.2.0 - #66

Merged
Alex1990 merged 1 commit into
mainfrom
release/v1.2.0
Sep 18, 2026
Merged

Alex1990 merged 1 commit into
mainfrom
release/v1.2.0

Conversation

@Alex1990

Copy link
Copy Markdown
Owner

1.1.0 → 1.2.0

@github-actions

Copy link
Copy Markdown
Contributor

Coverage

Metric % Covered / Total
Lines 91.73% 1121/1222
Statements 90.42% 1209/1337
Functions 92.76% 218/235
Branches 76.97% 575/747

@github-actions github-actions Bot added the needs-triage Maintainer needs to evaluate (loop can't decide; too risky; external PR) label Sep 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Loop triage — needs-triage (human-owned; the loop must not merge this one).

This is an owner-authored, same-repo release PR (release/v1.2.0 → main, chore(release): 1.2.0). Per docs/agents/ops.md / docs/agents/release.md, releases stay human-only — the loop only runs the read-only preflight — and the change is already written and green, so no agent-actionable work remains: only your review/merge (then pnpm release:tag / pnpm publish). Routing to the human inbox.

Verified read-only — the release checks out

  • Bump type is right: 1.1.0 → 1.2.0 (minor). The only user-visible change since v1.1.0 is d15d021 feat: add Volcano Engine TOS provider entry; everything else is docs/chore/test/ci. No major warranted.
  • Diff is release-only: git diff --stat origin/main HEAD = CHANGELOG.md +96, package.json ±1 (version 1.1.0 → 1.2.0). No source or .github/workflows/** changes.
  • Commit shape matches the new flow: single commit chore(release): 1.2.0, base a313e70 == current origin/main, and no v1.2.0 tag exists (latest tag is v1.1.0) — the tag is correctly deferred to pnpm release:tag after the merge.
  • Gates: pnpm lint → 0 warnings / 0 errors; pnpm fmt:check clean; pnpm build + pnpm check:types exit 0. CI on head 1721ff3: Lint pass, Test pass.
  • GitHub state: MERGEABLE, BLOCKED / REVIEW_REQUIRED, labels [], no reviews; the only comment is the coverage bot.

One non-blocking note: changelogen renders the internal chore(loop) / chore(ci) maintenance commits under "🏡 Chore" in the user-facing CHANGELOG.md — the tool's current default, in case you want the changelog curated before merge.

No ready-for-agent work exists. Nothing pushed or written by the loop.

@Alex1990
Alex1990 merged commit 759423e into main Sep 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-triage Maintainer needs to evaluate (loop can't decide; too risky; external PR)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant