Abandon a release or release candidate when you no longer want to promote the combined package. Gearset closes the package and reopens its features so they can continue through the pipeline individually.
Abandon the package
Open the appropriate pipeline environment:
For a release, open the final environment and select Releases.
For a release candidate, open the nominated penultimate environment and select Release candidates.
Open the three dots menu.
Choose the option to abandon release
Gearset closes the release branch and its pull request. It then reopens the feature pull requests that were included in the package against the relevant target environment.
What happens when you abandon a release or release candidate?
Gearset closes the release or release candidate and its pull request.
The included items are reopened against the environment where the package was abandoned.
Individual features are reopened as individual promotion pull requests.
An included bundle remains a bundle and is reopened as a single pull request.
If multiple pull requests use the same source branch, Gearset reopens one pull request containing all the relevant commits.
The features, bundles and their commits aren’t changed.
💡 If the release contains a bundle, Gearset reopens it as a bundle rather than as individual feature PRs. A bundle can only be separated or changed at its designated creation environment, before it is promoted further through the pipeline.
Abandon a release promoted from a release candidate
When promoted, a release candidate becomes a release in the final environment. If you abandon it:
Gearset closes the release in the final environment.
The included features and bundles are reopened against that final environment.
You can manage them individually or use them to create another release.