Release v1.1.0 #64

2026-07-02T05:29:50-05:00

jcwalker3 commented

2026-07-02 05:29:50 -05:00

Version bump and release notes for v1.1.0.

Closes #63.

Version bump and release notes for v1.1.0. Closes #63.

jcwalker3 added 1 commit 2026-07-02 05:29:51 -05:00

chore: version bump and release notes for v1.1.0 (fixes #63 ) afa57fa65c

sysadmin requested changes 2026-07-02 14:04:47 -05:00

sysadmin left a comment

Blocking this release PR for staleness. The branch is 8 commits behind current master and only adds CHANGELOG.md for an older v1.1.0 snapshot. Since then, master has gained additional merged work including the developer testing guide (#81), shared API pagination/failure handling (#83), LLM-Agent-SHA Phase 0 (#87), and Jenkins read-only design docs (#88). A release/version PR should be rebased or regenerated from current master so the changelog/release contents reflect the actual release surface before merge. I did not run the full release checks because this needs refresh first.

sysadmin reviewed 2026-07-02 14:10:50 -05:00

sysadmin left a comment

Do not merge as-is — release notes are stale. (Review comment, not an approval.)

State: head afa57fa, based at 2d5cb4b, now 8 commits behind master (007b5da). The PR adds a new CHANGELOG.md with v1.1.0 notes, so it applies cleanly (Gitea reports mergeable) — but the notes only cover work up to its base (#9 identity aliases, #3 provenance, #6 manage_labels modes, #56/#58 status:in-progress cleanup).

Missing from the v1.1.0 notes — all merged to master after this branch was cut:

#67 / PR #83 — shared API pagination + failure handling in gitea_auth.api_request/api_get_all (timeouts, DNS/network errors, 502/503/504, malformed JSON, redacted errors, bounded pagination). A real behavior change; must be in the release notes.
#70 / PR #81 — developer testing guidelines.
#72 / PR #88 — Jenkins read-only build-status tools design doc.
#86 / PR #87 — LLM-Agent-SHA attribution convention (Phase 0) + negative eligibility tests (345 → 355 tests).

Recommendation: update, don't close. On chore/issue-63-v1.1.0: rebase onto current master, extend the [v1.1.0] section with the four items above (plus anything merged in the interim), then hand off to a non-author reviewer for merge. No v1.1.0 tag should be cut from this branch's metadata until the updated PR merges — tags come from scripts/release-tag on the merge commit, per docs/release-workflows.md.

Review Metadata:

LLM-Agent-SHA: llm-a38fff25edeb
LLM-Role: reviewer
Authenticated-Gitea-User: sysadmin
MCP-Profile: prgs-reviewer
Eligibility: passed for comment (reviewer is not the PR author)

**Do not merge as-is — release notes are stale.** (Review comment, not an approval.) State: head `afa57fa`, based at `2d5cb4b`, now **8 commits behind master** (`007b5da`). The PR adds a new `CHANGELOG.md` with v1.1.0 notes, so it applies cleanly (Gitea reports mergeable) — but the notes only cover work up to its base (#9 identity aliases, #3 provenance, #6 manage_labels modes, #56/#58 status:in-progress cleanup). Missing from the v1.1.0 notes — all merged to master after this branch was cut: - **#67 / PR #83** — shared API pagination + failure handling in `gitea_auth.api_request`/`api_get_all` (timeouts, DNS/network errors, 502/503/504, malformed JSON, redacted errors, bounded pagination). A real behavior change; must be in the release notes. - **#70 / PR #81** — developer testing guidelines. - **#72 / PR #88** — Jenkins read-only build-status tools design doc. - **#86 / PR #87** — LLM-Agent-SHA attribution convention (Phase 0) + negative eligibility tests (345 → 355 tests). Recommendation: **update, don't close.** On `chore/issue-63-v1.1.0`: rebase onto current master, extend the `[v1.1.0]` section with the four items above (plus anything merged in the interim), then hand off to a non-author reviewer for merge. **No `v1.1.0` tag should be cut from this branch's metadata until the updated PR merges** — tags come from `scripts/release-tag` on the merge commit, per `docs/release-workflows.md`. Review Metadata: - LLM-Agent-SHA: llm-a38fff25edeb - LLM-Role: reviewer - Authenticated-Gitea-User: sysadmin - MCP-Profile: prgs-reviewer - Eligibility: passed for comment (reviewer is not the PR author)

jcwalker3 added 2 commits 2026-07-02 14:22:54 -05:00

Merge branch 'master' into chore/issue-63-v1.1.0 fd68c439b2

chore: refresh v1.1.0 release notes with all work merged since v1.0.1 (#63 ) 0cdbf63660

Merge current master (4f5b732) into the release branch and expand the
CHANGELOG v1.1.0 section to cover every merge since the v1.0.1 tag:
identity/eligibility tooling (#9, #11, #13, #14), gated review/merge
workflows (#15, #16), execution profiles (#12, #19), audit logging (#18),
Retry-After backoff (#27), API pagination + failure handling (#67),
release-tag helper (#50), status:in-progress automation (#56, #58),
LLM-Agent-SHA Phase 0 (#86), provenance helper (#3), manage_labels modes
(#6), and documentation (#8, #70, #72, #77).

PRs #82 (#68 release SOP) and #84 (#69 Linux portability) were closed
without merging and are intentionally NOT listed.

No feature code changed; CHANGELOG.md only. No tag created.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

jcwalker3 added 2 commits 2026-07-02 14:47:34 -05:00

Merge remote-tracking branch 'prgs/master' into chore/issue-63-v1.1.0 0d6d31d341

chore: add #73/#76/#79/#80 docs merges to v1.1.0 release notes (#63 ) d8269fc704

Master moved during release prep: PRs #89 (#79), #90 (#80), #92 (#76), and
#93 (#73) merged. Sync the branch with master (ba6064e) and record all four
in the v1.1.0 Documentation section. CHANGELOG.md only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

sysadmin reviewed 2026-07-02 14:48:09 -05:00

sysadmin left a comment

Approve. Reviewed head d8269fc (branch fully synced with master ba6064e, 0 behind).

Final PR diff against master: CHANGELOG.md only (+24 net). The two master-sync merge commits (fd68c43, 0d6d31d) brought master files in unchanged. No feature code, no secrets, no generated artifacts, no unrelated files. git diff --check clean.

Changelog validation — [v1.1.0] covers every merge since the v1.0.1 tag:

Added: #9, #11, #13, #14 (identity/eligibility tooling), #15 (gated review), #16 (gated merge: confirmation, pinning, self-merge block), #12/#19 (execution profiles), #18 (audit logging), #67 (API pagination + failure handling), #50 (release-tag helper), #56/#58 (status automation), #86 (LLM-Agent-SHA Phase 0), #3 (provenance helper), #6 (manage_labels modes). ✓
Changed: #27 (Retry-After backoff), #67 (paginated list tools), retained bullets. ✓
Documentation: #8, #70, #72, #77, plus the four that merged during release prep — #79 (safety/boundary), #80 (label taxonomy), #73 (GlitchTip read-only design), #76 (multi-service profile model). ✓

Independently verified exclusions: PR #82 (#68 release SOP) and PR #84 (#69 Linux portability) were closed without merging — docs/release-version-sop.md and docs/linux-container-portability.md are absent from master's tree and their commits absent from master history. Correctly NOT listed. (They'll belong to whichever release lands their re-rolled PRs.)

Checks (branch worktree at d8269fc): py_compile mcp_server/manage_labels/gitea_auth OK · bash -n scripts/clear-provenance OK · pytest tests/ -q 355 passed · git diff --check clean · staged-diff secret sweep clean. Tags verified still only v1.0.0/v1.0.1 — nothing pre-tagged.

PR body accepted as-is: terse but accurate (release notes for v1.1.0, closes #63); it makes no claim that excluded work landed.

Merging next via the gated merge tool; tag v1.1.0 will be cut from the resulting master merge commit via scripts/release-tag.

Review Metadata:

LLM-Agent-SHA: llm-a38fff25edeb
LLM-Role: reviewer/merger
Authenticated-Gitea-User: sysadmin
MCP-Profile: prgs-reviewer
Eligibility: passed (PR author jcwalker3 ≠ sysadmin)

Approve. Reviewed head `d8269fc` (branch fully synced with master `ba6064e`, 0 behind). Final PR diff against master: **`CHANGELOG.md` only** (+24 net). The two master-sync merge commits (`fd68c43`, `0d6d31d`) brought master files in unchanged. No feature code, no secrets, no generated artifacts, no unrelated files. `git diff --check` clean. Changelog validation — `[v1.1.0]` covers every merge since the `v1.0.1` tag: - Added: #9, #11, #13, #14 (identity/eligibility tooling), #15 (gated review), #16 (gated merge: confirmation, pinning, self-merge block), #12/#19 (execution profiles), #18 (audit logging), #67 (API pagination + failure handling), #50 (release-tag helper), #56/#58 (status automation), #86 (LLM-Agent-SHA Phase 0), #3 (provenance helper), #6 (manage_labels modes). ✓ - Changed: #27 (Retry-After backoff), #67 (paginated list tools), retained bullets. ✓ - Documentation: #8, #70, #72, #77, plus the four that merged during release prep — #79 (safety/boundary), #80 (label taxonomy), #73 (GlitchTip read-only design), #76 (multi-service profile model). ✓ Independently verified exclusions: PR #82 (#68 release SOP) and PR #84 (#69 Linux portability) were **closed without merging** — `docs/release-version-sop.md` and `docs/linux-container-portability.md` are absent from master's tree and their commits absent from master history. Correctly NOT listed. (They'll belong to whichever release lands their re-rolled PRs.) Checks (branch worktree at d8269fc): py_compile mcp_server/manage_labels/gitea_auth OK · `bash -n scripts/clear-provenance` OK · `pytest tests/ -q` **355 passed** · `git diff --check` clean · staged-diff secret sweep clean. Tags verified still only v1.0.0/v1.0.1 — nothing pre-tagged. PR body accepted as-is: terse but accurate (release notes for v1.1.0, closes #63); it makes no claim that excluded work landed. Merging next via the gated merge tool; tag `v1.1.0` will be cut from the resulting master merge commit via `scripts/release-tag`. Review Metadata: - LLM-Agent-SHA: llm-a38fff25edeb - LLM-Role: reviewer/merger - Authenticated-Gitea-User: sysadmin - MCP-Profile: prgs-reviewer - Eligibility: passed (PR author jcwalker3 ≠ sysadmin)

sysadmin merged commit 0e2840b76c into master

2026-07-02 14:48:34 -05:00

sysadmin referenced this pull request

2026-07-02 15:12:21 -05:00

feat: opt-in Docker-based Gitea integration test suite (#66) #97

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#64