chore: release v0.11.0

[mohanagy]

Summary

• Cuts v0.11.0, the first community-feature release of graphify-ts. Bundles #54 (OpenCode MCP installer support, by @jamemackson — already merged to main) with new infrastructure for crediting contributors.
• Adds an auto-updating contributors list via GitHub Actions, replacing the static Credit handling with a real HTML table that regenerates on every push to main.
• Updates CHANGELOG.md and package.json to satisfy the release workflow's tag/version/changelog validation, so a v0.11.0 tag will pass Validate tag, package version, and changelog.

What's in this release

Added — OpenCode MCP installer support (#54, @jamemackson)

graphify-ts opencode install now wires graphify-ts into OpenCode. The agent-installer matrix is now Claude Code · Cursor · Copilot · Gemini CLI · Aider · OpenCode. First community-contributed agent integration.

Added — Auto-updating contributors workflow

• New .github/workflows/contributors.yml running akhilmhdh/contributors-readme-action@v2.3.10 on push to main, weekly cron (Mon 03:00 UTC), and workflow_dispatch.
• README Contributors section now uses the action's <!-- readme: contributors -start/-end --> markers; the action commits a regenerated HTML table back to main after the next push, with no manual maintenance going forward.
• One-line shout-out preserved for @jamemackson as the inaugural community contributor.

Test plan

• CI passes (typecheck + tests + build + npm pack --dry-run)
• After merge to main: confirm the Update contributors workflow runs and commits a regenerated Contributors table containing both @mohanagy and @jamemackson
• Tag v0.11.0 from main and confirm the Release workflow passes the validation step (tag === v$VERSION, CHANGELOG section present)
• Confirm the GitHub release is created with auto-generated notes
• (Manual / out-of-band) npm publish for @mohammednagy/graphify-ts@0.11.0 once the GitHub release is live, unless an npm-publish workflow exists that I haven't seen

Notes

• Version bump is a minor (0.10.12 → 0.11.0). Past releases have used patches for changes of similar size; treating a new agent integration as minor is more semver-correct and gives this release a clean narrative anchor for the launch post.
• The contributors automation needs permissions: contents: write to commit back to main. Already configured in the workflow.

Summary by CodeRabbit

• New Features

  • Support for OpenCode agent-installer integration via the installer command.

• Documentation

  • Added a Contributors section to the README with an updated contributors list and a shout-out for a recent PR.

• Chores

  • Automated contributors list maintenance via a scheduled/triggerable workflow.

• Release

  • Bumped package version to v0.11.0.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR releases v0.11.0: bumps package.json version, adds a GitHub Actions workflow to auto-regenerate the README contributors list, adds a Contributors section to README, and updates CHANGELOG with the new release and an OpenCode installer entry.

Changes

Release v0.11.0 — Contributors automation + release metadata

Layer / File(s)	Summary
Release Metadata package.json	Version updated from 0.10.12 → 0.11.0.
Release Notes CHANGELOG.md	Added Unreleased and v0.11.0 (2026-05-05) section documenting OpenCode installer support and the contributors-list automation.
CI/CD Workflow .github/workflows/contributors.yml	New Update contributors workflow (triggers: push to main, weekly cron 0 3 * * 1, workflow_dispatch); sets permissions: contents: write, checks out full history (fetch-depth: 0), runs akhilmhdh/contributors-readme-action with use_username: true, image_size: 80, columns_per_row: 6, commits as docs: update contributors list.
Documentation README.md	Added ## Contributors section with <!-- readme: contributors -start --> / -end --> markers and an acknowledgment line referencing @jamemackson and PR #54.

Sequence Diagram(s)

sequenceDiagram
  participant Push as Developer / Push
  participant GH as GitHub
  participant Runner as Actions Runner
  participant Checkout as actions/checkout
  participant ContributorsAction as contributors-readme-action
  participant Repo as Repository (README.md)

  Push->>GH: push to main / schedule / manual dispatch
  GH->>Runner: start workflow (Update contributors)
  Runner->>Checkout: checkout repo (fetch-depth: 0)
  Runner->>ContributorsAction: run with params (use_username,image_size,columns)
  ContributorsAction->>Repo: update README contributors section
  ContributorsAction->>Runner: commit changes (docs: update contributors list)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• mohanagy/graphify-ts#43: Related release metadata and changelog updates.
• mohanagy/graphify-ts#41: Related version and release-documentation edits.
• mohanagy/graphify-ts#38: Related package version and changelog changes.

Poem

🐰 A tiny hop and version grows,
README glows with friends in rows,
A workflow wakes on nights and days,
To keep our credits in neat arrays,
Cheers to contributors—hip, hop, hoorays! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: releasing version 0.11.0, which is the primary objective of this pull request.
Description check	✅ Passed	The description includes Summary and detailed Test plan sections, but omits the Testing checklist and is missing explicit Checklist completion markers.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-0.11.0

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/contributors.yml:
- Around line 20-25: Replace the mutable action refs with immutable 40-character
commit SHAs: find the exact commit SHA for actions/checkout@v4 and for
akhilmhdh/contributors-readme-action@v2.3.10 in their respective repositories,
and update the uses lines to actions/checkout@<FULL_COMMIT_SHA> and
akhilmhdh/contributors-readme-action@<FULL_COMMIT_SHA>; keep the same inputs and
behavior but pin to the specific commits to prevent tag retargeting while
retaining the write permission in this workflow.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6313d15a-0f0e-49c4-a2a7-ae1d19521586

📥 Commits

Reviewing files that changed from the base of the PR and between 8bbfe5e and ff99532.

📒 Files selected for processing (4)

• .github/workflows/contributors.yml
• CHANGELOG.md
• README.md
• package.json

[coderabbitai]

🧹 Nitpick comments (1)

.github/workflows/contributors.yml (1)

15-17: ⚡ Quick win

Consider adding a concurrency group for this write-back job.

Because this job can be triggered by both push and schedule, overlapping runs can race and cause non-fast-forward push failures when both attempt to commit README updates.

Suggested patch

 name: Update contributors
 
 on:
   push:
@@
 permissions:
   contents: write
 
+concurrency:
+  group: update-contributors-main
+  cancel-in-progress: false
+
 jobs:
   update-contributors:
     runs-on: ubuntu-latest

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/contributors.yml around lines 15 - 17, Add a concurrency
group to the GitHub Actions job named "update-contributors" to prevent
overlapping runs from racing on write-back pushes; update the job definition for
update-contributors to include a concurrency block (unique group id, e.g.,
"update-contributors" or use context like github.ref + job name) and set
cancel-in-progress: true so a new run cancels any in-progress run before
starting.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.github/workflows/contributors.yml:
- Around line 15-17: Add a concurrency group to the GitHub Actions job named
"update-contributors" to prevent overlapping runs from racing on write-back
pushes; update the job definition for update-contributors to include a
concurrency block (unique group id, e.g., "update-contributors" or use context
like github.ref + job name) and set cancel-in-progress: true so a new run
cancels any in-progress run before starting.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 14d1d7dc-1994-4f0b-ad7d-1a5e0633d3c6

📥 Commits

Reviewing files that changed from the base of the PR and between ff99532 and 5228699.

📒 Files selected for processing (1)

• .github/workflows/contributors.yml