You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,11 +74,17 @@ In order to release a new version of this Action:
74
74
75
75
1. Locate the semantic version of the [upcoming release][release-list] (a draft is maintained by the [`draft-release` workflow][draft-release]).
76
76
77
-
2. Prepare a pull request to update [`action.yml`][action.yml] to reference the incoming version
77
+
2. Prepare a pull request to update [`action.yml`][action.yml] to reference the incoming version, get it approved, and merge it into the `main` branch.
78
78
79
-
3. Publish the draft release from the `main` branch with semantic version as the tag name, _with_ the checkbox to publish to the GitHub Marketplace checked. :ballot_box_with_check:
79
+
3. Publish the draft release **as a pre-release** from the `main` branch with semantic version as the tag name, _with_:
80
+
- the checkbox to publish to the GitHub Marketplace checked :ballot_box_with_check:
81
+
- :warning: _AND_ the checkbox to **Set as a pre-release** checked. :ballot_box_with_check:
80
82
81
-
4. After publishing the release, the [`release` workflow][release] will automatically run to create/update the corresponding the major version tag such as `v1`.
83
+
4. This will kick off a [Docker publishing workflow][docker-publish] for the newly created tag. Check the [associated workflow run list][docker-publish-workflow-runs] to verify the new Docker image is created successfully before moving on to the next step.
84
+
85
+
5. After the Docker image has been created with the new tag, find that [same pre-release][release-list] and edit it. Update it with the checkbox to **Set as the latest release** checked :ballot_box_with_check: and then publish it again.
86
+
87
+
6. After publishing it as the latest release, the [`release` workflow][release] will automatically run to create/update the corresponding the major version tag such as `v1`.
82
88
83
89
⚠️ Environment approval is required. Check the [Release workflow run list][release-workflow-runs].
84
90
@@ -88,7 +94,9 @@ The scripts and documentation in this project are released under the [MIT Licens
0 commit comments