Release BlogPost 2.29

[dimitrieh]

Description

Write the release announcement blog post for FlowFuse 2.29, releasing on April 9.

Epic/Story

Will be linked to parent tracking issue

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[dimitrieh]

Content Consideration

User-facing features (include in blog post)

#	Feature	Repo(s)	headline?	User outcome
1	Azure DevOps Git Integration	flowfuse#6896, #6846–#6849	Yes (#5491)	Push/pull flows to Azure DevOps repos and run pipelines — Git integration beyond GitHub
2	FlowFuse Expert for Self-Hosted Enterprise	CloudProject#1224, #1249, #1251, flowfuse#6949	Yes (product#57)	Self-hosted enterprise customers can now use FlowFuse Expert — contact your CS representative to get it enabled
3	Expert: Open by Default + State Persistence	flowfuse#6892	-	Expert opens automatically on first visit, remembers open/pinned state across sessions
4	MCP Server Discoverability Fix	flowfuse#6985	-	Older MCP servers are now visible to Expert Insights again
5	Embedded Editor Tab Title	flowfuse#7007, nr-assistant#231	-	Hosted/remote instance tabs show the actual Node-RED flow name
6	Blueprint Markdown Rendering	flowfuse#6991	-	Blueprint descriptions render as proper markdown
7	SSO Users' Roles Fix	flowfuse#6994	-	SSO-managed users' team roles can now be changed (customer-reported bug)
8	Node-RED 4.1.8	helm#856	-	Function node tab badges, theme plugin settings/menu overrides, palette categories via theme, show-first/last-tab actions, touch event fix on ports

Bug fixes & small updates (user-visible, not blog-worthy individually)

These are real improvements users can see, but too minor for the blog post. Could be mentioned in the changelog.

#	What	Repo	What changed for users
1	User menu z-index behind pinned Expert	flowfuse#6948	User menu was unclickable when Expert drawer was pinned — fixed
2	Expert agent mode switching reactivity	flowfuse#6894	Messages were lost when switching between agent modes — fixed
3	StreamableContent markdown rendering	flowfuse#6936	Expert responses rendered markdown incorrectly — fixed
4	npm username lowercase	flowfuse#6977	Users with uppercase npm usernames couldn't use private registry — fixed
5	Device count on user overview	flowfuse#7013	Device counts were missing from team overview — fixed
6	Certified Nodes sort order	flowfuse#6869	Certified nodes now always appear first in the palette
7	getProjectsToUpgrade matching	flowfuse#6870	Scheduled maintenance was incorrectly matching all projects — fixed

Not user-facing (internal / infrastructure)

No user-visible change. Excluded from blog and changelog.

#	What	Repo	Category
1	Expert Inline Actions (select, edit, search, add flow)	nr-assistant#184–#192, flowfuse#6864	FE built, but BE does not yet send triggering messages — not user-facing in 2.29
2	Expert default URLs baked into code	flowfuse#6949	Enables self-hosted Expert above, not separately visible
3	Rate limiting: team suspension & scheduled maintenance	flowfuse#6914, #6874, #6872	Backend reliability — prevents overloading, users don't see this
4	Expert scalability improvements	flowfuse#6839	Internal optimization
5	Pinia Migration Tasks 0–15	flowfuse	Internal Vuex→Pinia refactor
6	Reusable dialog/selection components	flowfuse#6891, #6930	Internal UI patterns
7	Sentry cross-origin SecurityError fixes	flowfuse#6851, #6888	Infrastructure bug fix
8	NodeJS v24 CI runtime	flowfuse#6946	CI/CD infrastructure
9	Helm extraObjects support	helm#849	Niche self-hosted ops
10	npm-registry custom ingress class	helm#863	Niche self-hosted ops
11	Container npm updates	various	Routine maintenance
12	Docs updates (Quick Start, RBAC, Azure)	various	Docs supporting features
13	~15 dependency bumps	various	Routine maintenance
14	MQTT PubSub migration (Expert)	~15 open issues	Won't ship in 2.29

Proposed blog structure

Two headline sections, then catch-all:

1. Azure DevOps Git Integration — headline
2. FlowFuse Expert for Self-Hosted Enterprise — headline
3. What else is new? — Node-RED 4.1.8, Expert opens by default, MCP fix, editor tab titles, blueprint markdown, SSO fix

Mapping to Product Planning

See the interactive tree at the internal research page showing how all items map to Product Planning Project #43.

[allthedoll]

closed by #4810