Repository navigation
Release v0.2.0, and a release playbook in docs/RELEASING.md - #21
Merged
Merged
Conversation
3 tasks done
CHANGELOG gets a 0.2.0 section for everything since v0.1.0 (GitHub runners, actions kept for GitHub outages, celld, SMTP, durable rate limits, gh and release-please, plugins for any instance) and an empty [Unreleased] section, with compare links on GitHub. The Worker, CLI, runner, packages, MCP server info and CITATION move to 0.2.0. README, ROADMAP and the self-hosting Updating docs cover what shipped and how to deploy a tagged version. docs/RELEASING.md is the step-by-step playbook for this and later releases; AGENTS.md and CONTRIBUTING.md point to it.
alankernel67
force-pushed
the
release/v0.2.0
branch
from
October 31, 2026 11:18
7aa563b to
94e3970
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Intent: name v0.2.0 for self-hosters, and keep the release process in the repository so later releases follow the same steps.
0.2.0 - 2026-10-31section covering everything since v0.1.0: GitHub runners, actions kept for GitHub outages, KVM,gh run/workflow/issue, release-please, environment settings, delete closed pull requests, plugins and extensions for any instance, celld, SMTP,RATE_LIMITS=durable, the contact form, Deploy workflow changes, and development moving to GitHub. Adds an empty[Unreleased]section and points the version links at GitHub instead of diffinery.com's inactive copy.diffinery --version), runner, packages, the MCP server'sserverInfo(and its docs), and CITATION.cff.self-hosting/deploy.md→ Updating explains deploying a tag, and that versions only move forward because of migrations.gh release createafter CI and Deploy pass onmain, plus extensions and plugins. AGENTS.md and CONTRIBUTING.md link to it.After merge, a maintainer tags the merge commit and publishes the GitHub release following steps 8 and 9 of the playbook. The release notes are drafted and ready.
How it was tested
pnpm -r buildandpnpm -r typecheckpass. Unit tests were run on Windows. workflow-yaml, git-core and vscode pass. The failures in cli, app and runner are Windows-only: CRLF checkouts, POSIX paths, file modes, symlinks, bash and bubblewrap. None involve the changed files. This PR's Linux CI runs the full suite.Checklist
pnpm -r typecheckpasses;pnpm -r testto be confirmed by CI on Linuxapps/diffinery/docsMade for Alan Kernel (@alankernel67).