Beta is where we ship and learn. v4.2.0 is our October update; Bitbucket is now a fully supported connector, closing the version control gap for teams not on GitLab. Node configuration auto-inherits in chained workflows, removing a persistent friction point. And backend security has been hardened across all services. Three things, done properly.

When we launched BluBees on the Atlassian Marketplace, we knew the real work was just beginning. Building something genuinely useful means getting it in front of real teams, watching how they use it, and iterating on what actually matters. That's what Beta is for. And today, we're sharing everything that's in it — MCP support, four AI models, Webhook Node, Conditional Routes, and a canvas built for everyone on your team.

Most software teams have automated parts of their release pipeline. The CI/CD runs automatically. Tests fire on merge. But the full pipeline — from the moment a customer reports something to the moment a fix is deployed and everyone who needs to know has been told — still has humans filling the gaps. Someone creates the Jira ticket. Someone updates the status. Someone notifies Slack. These aren't engineering tasks. They're coordination tasks. And they happen every single rele