chore: release 0.8.7

[steipete]

Prepare patch release 0.8.7 for September 5, 2026. Date the changelog, keep Fixes before Maintenance and contributor credit, and lead with the users.list pagination hang fix.

The runtime version remains injected by GoReleaser. A local release-version build reports 0.8.7; the changelog-only change passed independent P0–P2 review. The unified release workflow will run only after CI and Docker pass on the resulting main commit.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed September 5, 2026, 3:39 PM ET / 19:39 UTC.

ClawSweeper review

What this changes

Dates the 0.8.7 changelog and highlights the fix for Slack member-directory sync hanging on repeated page cursors.

Merge readiness

✅ Ready for maintainer review

Keep open: this is a focused, correct release-preparation patch that is not yet on the pinned main branch. No actionable defects were found, and the collaborator-authored PR is exempt from automatic cleanup.

Priority: P3
Reviewed head: 5e1369b776662c73ae23695f6349970f52f4635e

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused release-documentation patch with source-supported wording and no actionable findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: The collaborator-authored PR changes only changelog prose, so the external-contributor runtime-proof gate does not apply; its reported version build was not independently executed.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: The collaborator-authored PR changes only changelog prose, so the external-contributor runtime-proof gate does not apply; its reported version build was not independently executed.
Evidence reviewed	8 items	Verified introduced change: The complete pinned delta changes only the release heading and adds one highlight; existing fixes, maintenance notes, and contributor credit remain intact. Release preparation remains necessary: Pinned main still starts with Unreleased. Local version tags end at v0.8.6, matching the supplied latest-release metadata; no supplied merged replacement owns this release preparation. Highlight matches existing implementation: The member-list loop records page cursors and returns a clear error when one repeats. This source is unchanged by the PR.
Findings	None	None.
Security	None	None.

How this fits together

Slacrawl’s changelog describes changes included in each CLI release. Its separate release workflow builds and publishes versioned binaries, with GoReleaser injecting the runtime version.

flowchart LR
  A[Changes on main] --> B[Release changelog]
  B --> C[Release preparation PR]
  C --> D[Main branch]
  E[Manual version input] --> F[Release workflow]
  D --> F
  F --> G[Versioned CLI packages]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep the focused release notes and publish versioned artifacts through the repository’s established unified release workflow.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is release documentation; the highlighted runtime behavior is supported by existing source and regression tests.

Is this the best way to solve the issue?

Yes: dating the existing notes and adding a concise highlight is a narrow release-preparation change consistent with the target’s release process.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning medium; reviewed against 06db31fdcd10.

Labels

Label changes:

• add P3: This patch only prepares release documentation; it introduces no runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The collaborator-authored PR changes only changelog prose, so the external-contributor runtime-proof gate does not apply; its reported version build was not independently executed.

Label justifications:

• P3: This patch only prepares release documentation; it introduces no runtime behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The collaborator-authored PR changes only changelog prose, so the external-contributor runtime-proof gate does not apply; its reported version build was not independently executed.

Evidence

What I checked:

• Verified introduced change: The complete pinned delta changes only the release heading and adds one highlight; existing fixes, maintenance notes, and contributor credit remain intact. (CHANGELOG.md:3, 5e1369b77666)
• Release preparation remains necessary: Pinned main still starts with Unreleased. Local version tags end at v0.8.6, matching the supplied latest-release metadata; no supplied merged replacement owns this release preparation. (CHANGELOG.md:3, 06db31fdcd10)
• Highlight matches existing implementation: The member-list loop records page cursors and returns a clear error when one repeats. This source is unchanged by the PR. (internal/slackapi/api.go:973, 5e1369b77666)
• Existing regression coverage: Source inspection found tests for rejection after two repeated-cursor requests, successful distinct-cursor pagination, and longer cursor cycles. Tests were inspected, not executed. (internal/slackapi/api_test.go:1935, 5e1369b77666)
• Target release policy: CONTRIBUTING.md assigns tagging, packaging, signing, publication, and opening the next Unreleased section to the manual unified release workflow. The changelog preparation respects that boundary. (CONTRIBUTING.md:58, 5e1369b77666)
• Runtime version source: GoReleaser sets the CLI version through linker flags, supporting the PR’s explanation that no runtime version file needs updating. (.goreleaser.yml:21, 5e1369b77666)

Likely related people:

• steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• SebTardif: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.