[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-28。"],[[["\u003cp\u003eThis page covers the release process for both Apigee and Apigee hybrid products, including their respective versioning and update cadences.\u003c/p\u003e\n"],["\u003cp\u003eApigee follows a continuous release model with releases occurring approximately every two weeks, which are announced on the Apigee release notes page and can take four or more business days to roll out across all Google Cloud zones.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid releases follow a \u003ccode\u003emajor.minor.patch\u003c/code\u003e versioning scheme and have varying support levels and cadences depending on the release degree (Major, Minor, Patch, or Security Vulnerabilities).\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid runtime releases occur three times per year, approximately every four months, with monthly patch releases, and minor versions are supported for 12 months from their original release date.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee hybrid management plane will remain compatible with and be supported to work with a new hybrid runtime major/minor release for 12 months after the runtime minor version is published.\u003c/p\u003e\n"]]],[],null,["# Apigee release process\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nThis topic describes the release process for Apigee and Apigee hybrid.\n\nGetting release notifications\n-----------------------------\n\nThe best way to stay up to date on Apigee releases is to subscribe to the\nrelease notes RSS feed. To subscribe:\n\n1. Navigate to the Apigee release notes page.\n2. Select **All** to view all Apigee release notes, or select the Apigee product you wish to view.\n3. Add the URL of the page to your feed reader to subscribe to [All](/apigee/docs/release-notes) release notes, or to a specific release note category, such as [Apigee hybrid](/apigee/docs/hybrid/release-notes).\n\nApigee release process\n----------------------\n\nApigee follows a continuous release model to ensure our users can access the product innovation\nand enhancements quickly and at the highest quality possible.\n\n### Release cadence\n\nApigee releases occur approximately once every two weeks, though this timeframe may vary. Rollouts of Apigee releases are announced on the [Apigee release notes](/apigee/docs/release-notes) page\nwhen started, but may take four or more business days to complete across all Google Cloud zones.\nIndividual instances may not have the features and fixes available until the rollout is complete.\n\n### Release versioning\n\nReleases for Apigee use the following numbering scheme: \n\n```\nmajor_version.minor_version.patch_version\n```\n\nFor example, 3.2.1, where the major number is 3, the minor number is 2, and the patch number is\n1.\n\n\u003cbr /\u003e\n\nWhen viewing the instance version using the API or in the UI, you will see the version numbers converted to\na hyphenated string, such as `3-2-1-apigee-1`. The hyphenated version string is also used\nto announce releases and payloads in the [Apigee release notes](/apigee/docs/release-notes).\n\nApigee hybrid release process\n-----------------------------\n\n### Release versioning and cadence\n\nReleases for Apigee hybrid use the following numbering scheme: \n\n```\nmajor_version.minor_version.patch_version\n```\n\nFor example, 3.2.1, where the major number is 3, the minor number is 2, and the patch number is\n1.\n\n#### Apigee hybrid container images\n\n\n**Major, Minor, Patch Releases:** The container images used in these releases are integrated\nwith the Apigee hybrid Helm charts. Upgrading to any of these releases via the Helm chart\nautomatically updates the images. No manual image changes are typically needed.\n\n\n**Hotfix Releases:** For critical security and other immediate fixes, Apigee provides specific\ncontainer image tags that you must manually update in your existing deployments. The Helm chart\nbinary usually remains unchanged for hotfixes. Hotfixes are temporary and their changes will be\nincluded in the next major, minor, or patch release.\n\n\nSee [List the images in your repository](/apigee/docs/hybrid/v1.14/apigee-pull-push#list-the-images-in-your-repository) for information on determining the container image tags for your Apigee hybrid installation.\n\n### Supported versions and release history\n\n\nFor information about Apigee hybrid supported versions and\nrelease history, see [Apigee hybrid supported platforms and versions](/apigee/docs/hybrid/supported-platforms).\n\n### Runtime plane version support policy\n\nfiber_new\nApigee publishes a new minor (for example, y in version x.y) hybrid runtime\nrelease three times per year, approximately every four months,\nwith a monthly patch release (for example, z in version x.y.z). Apigee\nsupports minor versions for at most 12 months from their original\nrelease date. This is a recent update from the previous four times per\nyear and nine months of support.\n\n\nThe objective of the runtime plane version support policy is to allow customers the\nflexibility to schedule upgrades when it meets their business needs, while balancing the rapid\nevolution of Apigee (and its dependency on underlying components like Anthos and Anthos Service\nMesh).\n\n#### Runtime plane and Anthos version compatibility\n\n\nAn Apigee hybrid runtime minor version will be supported on a minimum of two Anthos and Anthos\nattached cluster versions.\n\n### Management plane compatibility and support timelines\n\n\nThe Apigee hybrid management plane will remain compatible with and be\nsupported to work with a new hybrid runtime major/minor release for\n12 months after the runtime minor version is published (or\nthe greater of the last three runtime releases and 12 months).\n\n\nA management plane upgrade may break a runtime minor version that was published 12 months or longer.\n\n\nAfter the support window expires, Apigee requires customers to upgrade to a current release. No\nsupport tickets will be accepted for any releases that are outside the support window."]]
