After a release or release candidate has been created, users can add more features by selecting an open pull request and choosing Add to release... from the promotion dialog. Alternatively, you can find the release in the Releases or release candidate tab and select Add to release.
Both options display the release pop-up in the pipelines UI. Here, you can specify which release to add features to, and what features to add. The Merge into release button will then add them to the referenced release branch.
After the additional features are merged into the release, the release will be revalidated against the target org.
Add a feature with an existing conflict
A feature with a conflict against the base branch might still be required because it depends on another feature already included in the package.
If you can’t add the feature from Open pull requests, try adding it from the Releases or Release candidates tab. If Gearset identifies a conflict, resolve it before completing the merge.
For more information, see Resolve merge conflicts in a release or release candidate.
Removing features from a Release or Release candidate
If you need to remove a feature from a release, for example because a validation failed after it was added, you can now remove it directly rather than abandoning and recreating the whole release.
💡 You can remove features from both releases and release candidates, but not from a release that was promoted from a release candidate.
To remove features from a release:
Select the release, click the 'more' icon and select
Remove features:
Select how many of the most recently added features you'd like to remove:
Click
Remove featuresto confirm.💡 You can only remove the most recently added features in order, starting with the most recently added. You can’t remove an individual feature from elsewhere in the release.
Before removing features
Gearset warns you when removing features could affect the package:
Some features may share commits or depend on changes from another feature. Removing one could cause the updated release to fail validation. Review any dependencies and revalidate the release after removing features.
Any conflict resolution currently in progress for the package will be closed. You can add those features again to the new release version afterward.
What happens after features are removed?
The removed features are reopened against the target environment as individual PRs like they created initially.
If there are bundles, it stays same as bundles when removed.
Gearset creates a new version of the release branch, such as
gs-bundle/[release-name]_v{N}.A new pull request is created for the updated package.
Existing approvals don’t carry over to the new pull request, so it must be reviewed again before promotion.
💡At least one feature must remain in the package. To remove every feature, abandon the release or release candidate instead.