After the main Agent release manager confirms successful deployment to a few targets, create a branch based on
master and run:
ddev agent changelog ddev agent integrations
Run the following commands to update the contents:
ddev agent changelog -w -fto update the existing
ddev agent integrations -w -fto update the existing
ddev agent integrations-changelog -wto add Agent version to existing
CHANGELOG.mdreleases of integrations.
Create a pull request and wait for approval before merging.
Only critical fixes are included in patches. See definition for critical fixes.
Releases after the final Agent release should be reserved for critical issues only. Cherry-picking commits and releases for the patch release is mostly similar to the process for preparing release candidates.
However, it's possible that from the time code freeze ended and a bugfix is needed, the integration has other non-critical commits or was released.
The next section will describe the process for preparing the patch release candidates.
Multiple check releases between bugfix release¶
Given the effort of QA-ing the Agent release, any new changes should be carefully selected and included for the patch.
Follow the following steps to add patch release:
- Cherry-pick the bugfix commit to the release branch.
Release the integration on the release branch.
- Make a pull request with integration release, then merge it to the release branch.
Remember to trigger the release pipeline and build the wheel. You can do so by tagging the release:
`ddev release tag <INTEGRATION>`
Note: only release PRs merged to master automatically build a wheel.
Then pull the latest release branch so your branch has both the bugfix commit and release commit.
Tag the branch with the new bumped version