fluid-release

Automate Fluid Framework client library releases by triggering a skill that manages version bumping, changelog generation, branch creation, and pull request workflows end-to-end. It supports both interactive step-by-step execution and fully autonomous modes for streamlined releases.

Yes, GitHub Actions can handle versioning and changelog generation for Fluid Framework. The release automation manages CI-specific command alternatives, creating branches and pull requests to integrate smoothly with your existing GitHub Actions workflows.

Preparing a minor Fluid Framework release involves automated release prep phases that bump versions, generate changelogs, and create necessary branches and pull requests. You can trigger this process interactively or autonomously, then prompt for final manual steps like queuing a build.

Yes, the Fluid Framework release process supports autonomous CI/CD workflows. It offers a fully automated mode that handles release preparation, execution, and post-release type test updates without requiring manual intervention, alongside an interactive guided mode.

When an automated Fluid Framework release fails in CI, the process provides fallback mechanisms by automatically creating GitHub issues. This ensures failures are tracked and documented, allowing developers to address errors without losing release context.

No, you do not need to manually update type tests after executing a Fluid Framework release. The automation includes post-release type test update phases, ensuring type definitions are synchronized across the released client libraries automatically.