oss/syft
2
0
Fork 0
mirror of https://github.com/anchore/syft.git synced 2026-10-31 06:26:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

Revert "Add docker image and refactor release pipeline (#310)"

Browse Source 
This reverts commit 6195002ae5.

Signed-off-by: Alex Goodman <wagoodman@users.noreply.github.com>
This commit is contained in:
Alex Goodman
2021-03-11 12:42:18 -05:00
committed by Alex Goodman
parent 6195002ae5
commit 5e62bca72f
14 changed files with 231 additions and 619 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASE.md
+6 -8
View File
@@ -44,7 +44,7 @@ for each release.
This project auto-generates the Changelog contents for each current release and posts the
generated contents to the GitHub Release page. Leveraging the GitHub Releases feature
allows GitHub to manage the Changelog on each release outside the git repository while
allows GitHub to manage the Changelog on each release outside of the git repository while
still being hosted with the released assets.
The Changelog is generated from the metadata from in-repository issues and PRs, using
@@ -89,13 +89,11 @@ This release process itself should be as automated as possible, and have only a
milestone with a partial version, the full version should be used for the git tag (e.g.
with a Milestone of `v0.1` the tag should be `v0.1.0`).
1. Push the tag.
1. A release admin must approve the release on the Github Actions release pipeline run page.
Once approved, the release pipeline will generate all assets and draft a GitHub Release.
1. Push the tag, the release pipeline will generate and publish all assets as well as a
draft GitHub Release.
1. Navigate to the Github Release draft page to review the final changelog and publish the
release. Once published, a release-follow-up pipeline will publish derivative artifacts
(docker image to DockerHub, brew formula to the external homebrew git repo, etc).
1. Promote the GitHub Release from draft to public. Note: since extra assets are made
available immediately from previous steps (i.e. the brew formula) the release should
only be in this state for a small amount of time (minutes).
1. If there is a release Milestone, close it.