[{"data":1,"prerenderedAt":282},["ShallowReactive",2],{"blog-\u002Fblog\u002F2023\u002F08\u002Fflowforge-1-10-release":3},{"id":4,"title":5,"body":6,"description":12,"extension":271,"meta":272,"navigation":277,"path":278,"seo":279,"stem":280,"__hash__":281},"blog\u002Fblog\u002F2023\u002F08\u002Fflowforge-1-10-release.md","FlowFuse 1.10 Release Now Available",{"type":7,"value":8,"toc":254},"minimark",[9,13,25,28,37,40,49,52,56,84,88,114,118,121,149,153,156,194,197,201,208,217,221,229,236,240],[10,11,12],"p",{},"FlowFuse 1.10 release includes improvements to device management and importing environment variable templates.",[14,15,17,18],"h2",{"id":16},"import-environment-variable-templates-#2372","Import Environment Variable Templates  ",[19,20,24],"a",{"href":21,"rel":22},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2372",[23],"nofollow","#2372",[10,26,27],{},"FlowFuse 1.10 now allows users to import environment variable templates. This makes it much easier and less error prone to maintain and add new environment variables to Node-RED instances running on FlowFuse.",[14,29,31,32],{"id":30},"devops-pipelines-now-can-include-devices-#2243","DevOps Pipelines now can include devices ",[19,33,36],{"href":34,"rel":35},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2243",[23],"#2243",[10,38,39],{},"DevOps pipelines have proven very popular for creating dev\u002Ftest\u002Fproduction environments for Node-RED flow development. Now, devices can be associated with a pipeline so when a snapshot is created it can be pushed to all the devices associated with the pipeline.  This will improve the overall quality and reliability of Node-RED development for remote devices.",[14,41,43,44],{"id":42},"devices-can-now-access-the-team-library-#2294","Devices can now access the team library ",[19,45,48],{"href":46,"rel":47},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2294",[23],"#2294",[10,50,51],{},"Team libraries allow Node-RED development team to share common flows and nodes through a shared library. Until the 1.10 release, Node-RED running remotely on a device did not have access to the team library. This limitation is now removed so device development can benefit from reusing standard flows.",[14,53,55],{"id":54},"other-new-features","Other New Features",[57,58,59,68,76],"ul",{},[60,61,62,63],"li",{},"Add description of device type field  ",[19,64,67],{"href":65,"rel":66},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2428",[23],"#2428",[60,69,70,71],{},"Improve reliability of device editor ",[19,72,75],{"href":73,"rel":74},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2483",[23],"#2483",[60,77,78,79],{},"Improve error feedback from device editor tunnel ",[19,80,83],{"href":81,"rel":82},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2473",[23],"#2473",[14,85,87],{"id":86},"bug-fixes","Bug Fixes",[57,89,90,98,106],{},[60,91,92,93],{},"Improve visualization of Last Seen & Last Known with large amounts of devices. ",[19,94,97],{"href":95,"rel":96},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2380",[23],"#2380",[60,99,100,101],{},"Fix billing information error in FlowFuse Cloud ",[19,102,105],{"href":103,"rel":104},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2416",[23],"#2416",[60,107,108,109],{},"Fix T&C checkbox on sign-up page ",[19,110,113],{"href":111,"rel":112},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F2419",[23],"#2419",[14,115,117],{"id":116},"community-contributions","Community Contributions",[10,119,120],{},"Thanks to our community members for their contributions to this release.",[57,122,123,136],{},[60,124,125,130,131],{},[19,126,129],{"href":127,"rel":128},"https:\u002F\u002Fgithub.com\u002Fdfulgham",[23],"dfulgham"," - Added support for annotation substitutions ",[19,132,135],{"href":133,"rel":134},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowforge-driver-k8s\u002Fpull\u002F95",[23],"#95",[60,137,138,143,144],{},[19,139,142],{"href":140,"rel":141},"https:\u002F\u002Fgithub.com\u002Felenaviter",[23],"elanaviter"," - Editors: allow optional service account linkage ",[19,145,148],{"href":146,"rel":147},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowforge-driver-k8s\u002Fpull\u002F92",[23],"#92",[14,150,152],{"id":151},"what's-next?","What's next?",[10,154,155],{},"We're always working to enhance your experience with FlowFuse. Here's how you can stay informed and contribute:",[57,157,158,170,182],{},[60,159,160,164,165,169],{},[161,162,163],"strong",{},"Roadmap Overview",": Check out our ",[19,166,168],{"href":167},"\u002Fchangelog\u002F","Product Roadmap Page"," to see what we're planning for future updates.",[60,171,172,175,176,181],{},[161,173,174],{},"Entire Roadmap",": Visit our ",[19,177,180],{"href":178,"rel":179},"https:\u002F\u002Fgithub.com\u002Forgs\u002FFlowFuse\u002Fprojects\u002F5",[23],"Roadmap on GitHub"," to follow our progress and contribute your ideas.",[60,183,184,187,188,193],{},[161,185,186],{},"Feedback",": We're interested in your thoughts about FlowFuse. Your feedback is crucial to us, and we'd love to hear about your experiences with the new features and improvements. Please share your thoughts, suggestions, or report any ",[19,189,192],{"href":190,"rel":191},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002Fnew\u002Fchoose",[23],"issues on GitHub",".",[10,195,196],{},"Together, we can make FlowFuse better with each release!",[14,198,200],{"id":199},"try-it-out","Try it out",[10,202,203,204,193],{},"We're confident you can have self managed FlowFuse running locally in under 30 minutes.\nYou can install FlowFuse yourself via a variety of install options. You can find out more details ",[19,205,207],{"href":206},"\u002Fdocs\u002Finstall\u002Fintroduction\u002F","here",[10,209,210,211,216],{},"If you'd rather use our hosted offering: ",[19,212,215],{"href":213,"rel":214},"https:\u002F\u002Fapp.flowfuse.com\u002Faccount\u002Fcreate",[23],"Get started for free"," on FlowFuse Cloud.",[14,218,220],{"id":219},"upgrading-flowfuse","Upgrading FlowFuse",[10,222,223,228],{},[19,224,227],{"href":225,"rel":226},"https:\u002F\u002Fapp.flowfuse.com",[23],"FlowFuse Cloud"," is already running 1.10.",[10,230,231,232,193],{},"If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a\nguide for ",[19,233,235],{"href":234},"\u002Fdocs\u002Fupgrade\u002F","upgrading your FlowFuse instance",[14,237,239],{"id":238},"getting-help","Getting help",[10,241,242,243,247,248,253],{},"Please check FlowFuse's ",[19,244,246],{"href":245},"\u002Fdocs\u002F","documentation"," as the answers to many questions are covered there. Additionally you can go the the ",[19,249,252],{"href":250,"rel":251},"https:\u002F\u002Fdiscourse.nodered.org\u002Fc\u002Fvendors\u002Fflowfuse\u002F24",[23],"community forum"," if you have\nany feedback or feature requests.",{"title":255,"searchDepth":256,"depth":256,"links":257},"",2,[258,260,262,264,265,266,267,268,269,270],{"id":16,"depth":256,"text":259},"Import Environment Variable Templates  #2372",{"id":30,"depth":256,"text":261},"DevOps Pipelines now can include devices #2243",{"id":42,"depth":256,"text":263},"Devices can now access the team library #2294",{"id":54,"depth":256,"text":55},{"id":86,"depth":256,"text":87},{"id":116,"depth":256,"text":117},{"id":151,"depth":256,"text":152},{"id":199,"depth":256,"text":200},{"id":219,"depth":256,"text":220},{"id":238,"depth":256,"text":239},"md",{"navTitle":5,"excerpt":273},{"type":7,"value":274},[275],[10,276,12],{},true,"\u002Fblog\u002F2023\u002F08\u002Fflowforge-1-10-release",{"title":5,"description":12},"blog\u002F2023\u002F08\u002Fflowforge-1-10-release","iJ4pbNhWQNZQgr05NzkiB5KLvNhXLaaIL5RKdovYI0k",1780132425789]