pack orb before publish

Signed-off-by: Javier Romero <[email protected]>

Author: jromero

.circleci/config.yml

@@ -111,10 +111,20 @@ workflows:
   publish:
     unless: << pipeline.parameters.run-integration-tests >>
     jobs:
+      - orb-tools/pack:
+          filters:
+            branches:
+              ignore: /.*/
+            tags:
+              only: /^\d+\.\d+\.\d+$/
       - orb-tools/publish:
           orb-ref: buildpacks/pack@$CIRCLE_TAG
+          attach-workspace: true
+          checkout: false
           filters:
             branches:
               ignore: /.*/
             tags:
               only: /^\d+\.\d+\.\d+$/
+          requires:
+            - orb-tools/pack

RELEASE.md

@@ -1,7 +1,7 @@
 ## Release Process
 
 1. Create and push `release/<VERSION>` branch off of `main`.
-    _This will trigger a workflow that creates a draft release on GitHub._
+1. After all [CI checks](https://app.circleci.com/pipelines/github/buildpacks/pack-orb) pass, find the job "hold-for-approval" and `Approve`.
 1. On the [GitHub releases page](https://github.com/buildpacks/pack-orb/releases):
     1. Click `Edit` on the latest _draft_ release.
     1. Review (and edit) generated changelog.
@@ -13,9 +13,7 @@
     _The release "Publish" action will create a tag that then triggers a workflow that additionally publishes the orb to the circleci catalog._
 1. Confirm that the orb is updated by viewing the [orb page](https://circleci.com/developer/orbs/orb/buildpacks/pack).
 
-
 ## Makefile targets
 
-
 `make future-version` - logic to determine the next version by looking at the current git branch.
 `make generate-changelog` - process of generating the changelog for the `future-version`.