📦 v3.5.0

AI-Powered Content Pipelines & GraphQL Enhancements

Introducing automated content workflows, faster edge delivery, and major improvements to our GraphQL API. Read the full breakdown below.

Published Nov 14, 2024
Author DevRel Team
Version 3.5.0 (Stable)
Tags
GraphQL AI API Performance
Table of Contents

📋 Overview

Version 3.5.0 brings a significant leap in how FlowCMS handles content orchestration. We've rebuilt our pipeline engine from the ground up to support AI-assisted transformations, reduced API latency by 40%, and introduced native support for GraphQL subscriptions in real-time content feeds.

This release is fully backward compatible with v3.4.x, though we highly recommend reviewing the breaking changes section if you're utilizing custom middleware or legacy REST endpoints.

💡 Pro Tip

Check out our migration guide to automatically update your existing content models to leverage the new AI workflow triggers.

🚀 New Features

AI-Powered Content Pipelines

Create automated workflows that trigger on content publish, update, or deletion. Use our new @trigger directive to pipe content through AI summarization, image optimization, or multilingual translation without writing custom code.

graphql
type Article @model {
  id: ID!
  title: String!
  body: Markdown!
  summary: String @ai(generate: "summary", maxTokens: 150)
  translations: [Translation!] @trigger(event: "publish", action: "translate")
}

GraphQL Subscriptions & Real-Time Feeds

Stream content changes directly to your frontend or edge functions. Subscriptions now support filtering by content type, author, and custom metadata fields.

javascript
const { data } = useSubscription(
  gql`
    subscription OnContentPublished($contentType: String!) {
      contentPublished(contentType: $contentType) {
        id
        title
        status
        publishedAt
      }
    }
  `,
  { variables: { contentType: "blog_post" } }
);
console.log("New content:", data?.contentPublished);

Edge Cache Purge API

Purge specific CDN paths instantly via our new REST endpoint. Supports glob patterns and tag-based invalidation for precise cache management.

⚡ Improvements

🐛 Bug Fixes

⚠️ Breaking Changes

⚠️ Action Required

The following changes require code updates before upgrading.

Legacy REST Endpoints Deprecation

The /api/v1/content route has been officially removed. All clients must migrate to /api/v2 or the GraphQL endpoint. The v1 schema will return 410 Gone effective immediately.

Authentication Header Change

Bearer tokens must now be prefixed with FlowBearer instead of Bearer. Update your HTTP clients accordingly:

http
Authorization: FlowBearer sk_live_8x92kLm...

Environment Variables Rename

FLOW_API_KEY is now FLOWCMS_TOKEN. The old variable will be ignored in v3.5+.

📦 Upgrade Instructions

Upgrade using your preferred package manager or CLI. The process typically takes 2-5 minutes depending on your project size.

bash
# Using npm
npm install @flowcms/sdk@latest

# Using CLI
flowcms upgrade --version 3.5.0

# Verify installation
flowcms doctor

After upgrading, run a local build to verify compatibility. If you encounter schema mismatches, use the auto-migration tool:

bash
flowcms migrate --auto --dry-run
⚠️ Warning

Always back up your content database and configuration files before running migrations in production environments.

Ready to upgrade your workflow?

Deploy v3.5.0 today and experience faster content delivery, smarter automation, and a more powerful API.