GForge 26.0 Released
Your project context, live in your AI tools
The new GForge CLI puts your tickets, wiki, and project history directly inside Claude Code and Cursor. Plus a rebuilt Markdown editor, richer tickets, and Jenkins integration that closes the loop on CI.
Claude Code and Cursor can now see your tickets, wiki, and branches
The gforge CLI ships a built-in MCP (Model Context Protocol) server. Run gforge mcp and your AI coding assistant gets structured, authenticated access to your GForge instance — without leaving your editor.
Because it runs against your installation, behind your firewall, your project data never leaves your environment. Your AI sees exactly what you have permission to see.
- Ten built-in workflow prompts — design, code review, sprint status, release notes, bug investigation, and more
- First-run wizard writes
.mcp.jsonautomatically for Claude Code auto-discovery - Read and write tickets, wiki pages, branches, SCM diffs, and project briefs
- macOS, Linux, and Windows — single binary, no runtime
Using the GForge MCP: fetch ticket #64027, list its notebook pages, read the design doc, and give me a technical summary of what’s been designed and what the next steps are.
Assignee: Michael Tutty · Milestone: GForgeNext 26.1 · Status: Accepted
Work branch: rest/webhook-plumbing-#64027
What it is: An outbound event delivery system that fires HTTP callbacks when domain events occur — SCM pushes, ticket changes, wiki edits. Subscriptions are configured at site or project level, support wildcard patterns (scm.*, *.*.created), and cascade down the project hierarchy.
Key design decisions locked in:
- Two new tables only —
event_subscriptionandevent_delivery. No existing table changes. - At-least-once delivery with configurable retry/backoff (data-driven, not hardcoded).
- HMAC-SHA256 signed payloads with
${PLACEHOLDER}token substitution in URLs. - Steps 1–2 merged as of today: SQL migration and Doctrine entity models.
Critical path: Steps 3–6 — EventBusService::emit(), EventPatternMatcher, and the cascading subscription resolver. Nothing downstream can be tested end-to-end without these.
The whole platform now speaks Markdown
The wiki editor has been rebuilt from scratch using Toast UI. Write in Raw Markdown, switch to WYSIWYG, or use Side-by-Side with a live preview pane that updates as you type. A formatting toolbar, GForge macro browser, and Markdown Guide are all built in.
The same editor is now used for ticket descriptions, follow-ups, and notebook pages. Your team writes consistently formatted content everywhere in GForge — not just in the wiki.
- Existing HTML pages continue to render correctly
- One-click HTML → Markdown migration with guided preview
- Unsaved-changes detection with warning before navigating away
- Full GForge macro support including the new
ti-listembed
Click to enlarge
Every ticket now has a workspace
Tracker items in GForge 26.0 have a new Notebook tab — a structured workspace for the material that surrounds the work: design notes, investigation findings, test plans, meeting summaries, reference documents.
Notebook pages are full Markdown wiki documents with version history. Add as many named pages as you need. Attach files and preview them inline. Every change is recorded in the ticket’s audit trail.
- Multiple named, versioned Markdown pages per ticket
- File attachments with inline preview — no downloading to see what something is
- Full audit trail tied to the ticket timeline
- Badge on the tab shows page count at a glance
Click to enlarge
Gate any workflow transition behind a human decision
Workflow transitions can now require explicit approval before they complete. Project admins configure this per-transition. When triggered, the ticket enters a pending state with an approval panel showing validation feedback. Every approval and rejection is timestamped and recorded on the ticket timeline.
Useful for QA gates, change management, regulated deployments, or any process where a ticket should not advance without a deliberate human sign-off — and where you need an audit trail proving that decision was made.
More from this release
Across Jenkins, CI/CD, collaboration, and administration.
Jenkins Plugin 2.3
New FRS pipeline actions — download and upload File Release packages directly from Jenkins pipelines — with full multibranch pipeline and DSL support. Also fixes a bug where multibranch pipeline jobs weren’t triggering build notifications in GForge.
Favorites
Bookmark any object in GForge — tickets, wiki pages, projects, trackers, sprints, repositories — and reach it from the navigation bar in one click. Per-user, drag-to-reorder, persists across sessions.
@Mention Entire Roles
Type @ in any ticket description or follow-up to mention an entire project role. Every member of that role receives a notification. Autocomplete shows users and roles together so you find the right audience fast.
Record Deployments from the Terminal
gforge deploy post <project> <revision> walks every commit in a revision, finds all open tickets whose commits intersect that set, and stamps a deployment event on each ticket’s timeline automatically. Supports multiple environments via --level.
And more
OIDC Improvements
Custom claim mapping for non-standard identity providers (Azure AD, Okta). OIDC-authenticated users are no longer incorrectly prompted for a local password.
German & French
Full German UI translation added. French translation overhauled for accuracy and consistency across the platform.
Let’s Encrypt
Automatic SSL certificate provisioning and renewal for self-hosted installations. New helper scripts handle issuance and renewal.
Conventional Commits
Enable per-repository to reject non-conforming commit messages at push time. Keeps history machine-readable for automated changelogs and semantic versioning.
GForge 26.0 is available now
Download the CLI, read the full release notes, or ask our AI assistant anything about the release.
Questions? Visit gforge.com/ask-ai or contact support.