Skip to content

Latest commit

 

History

History
40 lines (29 loc) · 1.99 KB

RELEASING.md

File metadata and controls

40 lines (29 loc) · 1.99 KB

Releasing

Main Release

The following steps should be followed to release the main version:

  1. Run the workflow Prepare Release Main Version, to prepare the release. It creates a pull request updating the version and indicating the remaining release tasks;
  2. Finish the tasks indicated in the pull request;
  3. Merge the pull request, to create the tag and the draft release (done by Release Main Version);
  4. Verify the draft release;
  5. Publish the release.

Once published the Handle Release workflow will trigger the update of the marketplace with the new release, it will also create a pull request preparing the next development iteration.

Weekly Release

The following steps should be followed to release the weekly:

  1. Run the workflow Release Weekly, to create the tag and the draft release;
  2. Verify the draft release;
  3. Publish the release.

Once published the Handle Release workflow will trigger the update of the marketplace with the new release.

Docker Images

The image owasp/zap2docker-live is automatically built from the default branch.

The images owasp/zap2docker-weekly, owasp/zap2docker-stable, and owasp/zap2docker-bare are automatically built after the corresponding release to the marketplace.
The images owasp/zap2docker-stable and owasp/zap2docker-bare are built at the same time.

They can still be manually built by running the corresponding workflow: