[{"data":1,"prerenderedAt":100},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fmain\u002Frelease":3},{"id":4,"title":5,"body":6,"description":88,"extension":89,"group":90,"meta":91,"navigation":92,"order":93,"path":94,"section":95,"seo":96,"source":97,"stem":98,"version":21,"__hash__":99},"docs\u002Fdocs\u002Fmain\u002Frelease.md","Release status",{"type":7,"value":8,"toc":79},"minimark",[9,14,23,27,36,40,53,57,67,71],[10,11,13],"h2",{"id":12},"development-snapshot","Development snapshot",[15,16,17,18,22],"p",{},"The reviewed framework source has no published release. These guides target a particular ",[19,20,21],"code",{},"main"," commit and show how to pin it as a Go dependency. Do not assume a version mentioned by a generator default is available from a module proxy.",[10,24,26],{"id":25},"choose-a-dependency-deliberately","Choose a dependency deliberately",[15,28,29,30,35],{},"Use the ",[31,32,34],"a",{"href":33},"\u002Fdocs\u002Fmain\u002Finstallation\u002F","installation guide"," to pin the reviewed commit. When release tags become available, select an actual published version and review its changelog, compatibility notes and verification record before upgrading.",[10,37,39],{"id":38},"verify-your-application-environment","Verify your application environment",[15,41,42,43,47,48,52],{},"The upstream release policy describes configured verification targets and outstanding checks; configured targets alone do not prove runtime support. Check your own operating system, database, TLS\u002Fproxy configuration and resource lifecycles. See ",[31,44,46],{"href":45},"\u002Fdocs\u002Fmain\u002Fdeployment\u002F","deployment"," and ",[31,49,51],{"href":50},"\u002Fdocs\u002Fmain\u002Fsecurity\u002F","security",".",[10,54,56],{"id":55},"looking-for-the-maintainer-checklist","Looking for the maintainer checklist?",[15,58,59,60,52],{},"Framework CI gates, contracts-module releases, generated baselines and release preparation belong in ",[61,62,63],"strong",{},[31,64,66],{"href":65},"\u002Fdocs\u002Fmain\u002Fcontribute\u002Freleases\u002F","Contribute to Gonex → Maintaining releases",[10,68,70],{"id":69},"production-readiness-evidence","Production-readiness evidence",[15,72,73,74,78],{},"Review the ",[31,75,77],{"href":76},"\u002Fdocs\u002Fmain\u002Fproduction-readiness\u002F","hardening status and open release gates",". Technical implementation, a green CI run and an independently reviewed production release are separate milestones.",{"title":80,"searchDepth":81,"depth":81,"links":82},"",2,[83,84,85,86,87],{"id":12,"depth":81,"text":13},{"id":25,"depth":81,"text":26},{"id":38,"depth":81,"text":39},{"id":55,"depth":81,"text":56},{"id":69,"depth":81,"text":70},"Understand the current Gonex development snapshot, dependency pinning and support considerations for application developers.","md","REFERENCE",{},true,190,"\u002Fdocs\u002Fmain\u002Frelease","build",{"title":5,"description":88},null,"docs\u002Fmain\u002Frelease","mGbKMyYIguAjFbPfGlwW1cN-SiPmfaGUPoipOsdk0Uk",1792521640143]