fluo-release-operations

name	fluo-release-operations
description	fluo release operations knowledge pack. Captures Changesets, Version Packages PR, GitHub Actions-only publish, and release metadata sources.
compatibility	opencode
metadata	{"language":"en","domain":"operations","mode":"knowledge"}

Fluo Release Operations

This skill provides the knowledge required for managing releases within the fluo repository. It enforces the "Changesets-only" workflow and prevents unsafe local publishing.

Core Policies

1. Changesets ONLY: The sole source of truth for versioning and changelogs.
2. No Local Publish: npm publish must NEVER be run locally. All publishing is handled via GitHub Actions.
3. GitHub Actions Authority: The canonical release workflow is located at .github/workflows/release.yml.

Release Lane Policy

• Single main release lane: Stable patch, minor, and major releases flow through main and the canonical Changesets GitHub Actions workflow.
• Changeset intent is authoritative: patch, minor, and major changesets may all target main; reviewers must verify the semver intent matches the behavioral impact.
• Major release approval: PRs carrying major changesets require explicit maintainer approval and consumer-facing migration notes before merge.
• Check generated Version Packages PRs: Before approving or merging a Version Packages PR, verify its generated packages/*/package.json version deltas and changelog entries match the committed changesets.
• Release sequence: Merge implementation PRs with changesets to main, allow the Changesets action to create or update the Version Packages PR, then merge that Version Packages PR to publish through GitHub Actions.
• Future prerelease trains: Use Changesets prerelease mode and a dedicated workflow only when maintainers explicitly decide to publish next, beta, or rc dist-tags.

Release Lane Verification

• Run pnpm verify:changeset-release-lane -- --lane=stable --base-ref=<ref> in PR CI and release automation.
• The stable verifier accepts patch, minor, and major bumps, while still parsing pending .changeset/*.md files and generated packages/*/package.json version deltas.
• --lane=prerelease remains available for future prerelease workflow checks.
• A failing lane check is not a reason to downgrade semver. Fix malformed release metadata or generated package version data instead.

Release Metadata Sources

• Changesets: .changeset/*.md files define pending releases.
• Config: .changeset/config.json contains the workspace release configuration.
• Changelogs: Package-level CHANGELOG.md files are generated by the release process.
• Governance: docs/contracts/release-governance.md defines the overarching release policy.

Workflow knowledge

• Version Packages PR: A PR automatically generated by the Changesets bot that consumes pending .changeset/*.md files and updates package versions.
• Version Packages PR: A PR targeting main; it may contain patch, minor, and major deltas that match committed changesets.
• Publish Workflow: Triggered after the "Version Packages" PR is merged to main; this publishes the stable release through GitHub Actions.
• Release Intents: tooling/release/intents/*.json are legacy references and should not be used as the primary source of truth for new work.

Checklist for Changeset Creation

• Identify all affected public @fluojs/* packages.
• Determine the semver bump level (patch, minor, major) based on the behavioral contract impact.
• Provide a clear, human-readable summary of the change in the changeset file.
• Ensure the changeset is committed alongside the functional changes.