Skip to content

docs: Add RELEASE_PROCESS.md#4271

Draft
gregfurman wants to merge 1 commit into
hatchet-dev:mainfrom
gregfurman:docs/release-process
Draft

docs: Add RELEASE_PROCESS.md#4271
gregfurman wants to merge 1 commit into
hatchet-dev:mainfrom
gregfurman:docs/release-process

Conversation

@gregfurman

Copy link
Copy Markdown
Collaborator

Description

Adds a new RELEASE_PROCESS.md that outlines how we release new SDK and hatchet platform versions.

Type of change

  • Documentation change (pure documentation change)

What's Changed

  • Included new top-level document that outlines the hatchet release process.

Checklist

Changes have been:

  • Tested (unit, integration, or manually with steps specified)
  • Linted and formatted
  • Documented (where applicable)
  • Added to CHANGELOG (where applicable) -- see Keep a Changelog

🤖 AI Disclosure
  • I acknowledge that an LLM was used in the creation of this Pull Request, in accordance with Hatchet's AI_POLICY.md.
  • Details: Claude code was used to ensure the full release process was properly reflected in the new doc.

@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

@gregfurman is attempting to deploy a commit to the Hatchet Team on Vercel.

A member of the Team first needs to authorize it.

@gregfurman gregfurman force-pushed the docs/release-process branch from 3ed98d6 to 2669882 Compare June 24, 2026 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant