fix(oci): the Marketplace publish needs no manual step

Submitting the draft listing revision starts the publishing: the new
package lands in the "Publish in Progress" stage and Oracle carries it
to Live. The job summary and the Mattermost notification claimed the
opposite - "submitted for review ... Publish it from there manually
once it is approved" - which sent readers looking for a Console action
that does not exist.

Reword the status in oci-marketplace-steps (used by the unified
oci-build-release-test-publish.yml) and in the standalone
oci-marketplace-publish.yml, keeping the two in sync, and drop the same
claim from the OCI docs and the scheduled-builds note (only Azure Live
publishing stays manual).

The debug/warning lines around the submit call keep their wording: they
describe the submit-listing-revision-for-review CLI operation, and a
failed submission really does need a manual retry from the Console.

Author: yuravk

.github/actions/oci-marketplace-steps/action.yml

@@ -623,10 +623,10 @@ runs:
           echo "- **Revision Package**: \`${{ env.PACKAGE_VERSION }}\` (\`${{ env.PACKAGE_ID }}\`)"
           echo ""
           echo "### Status"
-          echo "✅ Draft revision created, package added, and submitted for review."
+          echo "✅ Draft revision created, package added, and submitted for publishing."
           echo ""
-          echo "Check it on the [Oracle Cloud Console](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ inputs.OCI_CLI_REGION }})"
-          echo "Publish it from there manually once it is approved"
+          echo "The new package is in the **Publish in Progress** stage - no manual action required."
+          echo "Track it on the [Oracle Cloud Console](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ inputs.OCI_CLI_REGION }})"
         } >> "$GITHUB_STEP_SUMMARY"
 
     - name: Send notification to Mattermost
@@ -647,6 +647,6 @@ runs:
           **Draft Revision**: [${{ env.LISTING_REVISION_NAME }}](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ inputs.OCI_CLI_REGION }})
           **Revision Package**: `${{ env.PACKAGE_VERSION }}` (`${{ env.PACKAGE_ID }}`)
 
-          ✅ Draft revision created, package added, and submitted for review.
-          Check it on the [Oracle Cloud Console](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ inputs.OCI_CLI_REGION }})
-          Publish it from there manually once it is approved
+          ✅ Draft revision created, package added, and submitted for publishing.
+          The new package is in the **Publish in Progress** stage - no manual action required.
+          Track it on the [Oracle Cloud Console](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ inputs.OCI_CLI_REGION }})

.github/workflows/oci-marketplace-publish.yml

@@ -1233,10 +1233,10 @@ jobs:
           echo ""
           echo "### Status"
           if [[ "${{ inputs.release_to_marketplace }}" == "true" ]]; then
-            echo "✅ Draft revision created, package added, and submitted for review."
+            echo "✅ Draft revision created, package added, and submitted for publishing."
             echo ""
-            echo "Check it on the [Oracle Cloud Console](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ vars.OCI_CLI_REGION }})"
-            echo "Publish it from there manually once it is approved"
+            echo "The new package is in the **Publish in Progress** stage - no manual action required."
+            echo "Track it on the [Oracle Cloud Console](${{ env.OCI_PUBLISHER_BASE_URL }}/listing/${{ env.LISTING_OCID }}/${{ env.DRAFT_REVISION_ID }}?region=${{ vars.OCI_CLI_REGION }})"
           else
             if [[ "${{ inputs.image_source_type }}" == "QCOW2 file URL" ]]; then
               echo "❌ **Marketplace release was not requested** (only Compute Image import and Object Storage upload performed)"
@@ -1266,9 +1266,9 @@ jobs:
           ${{ inputs.release_to_marketplace && format('**Draft Revision**: [{0}]({1}/listing/{2}/{3}?region={4})', env.LISTING_REVISION_NAME, env.OCI_PUBLISHER_BASE_URL, env.LISTING_OCID, env.DRAFT_REVISION_ID, vars.OCI_CLI_REGION) || '' }}
           ${{ inputs.release_to_marketplace && format('**Revision Package**: `{0}` (`{1}`)', env.PACKAGE_VERSION, env.PACKAGE_ID) || '' }}
 
-          ${{ inputs.release_to_marketplace && '✅ Draft revision created, package added, and submitted for review.' || '' }}
-          ${{ inputs.release_to_marketplace && format('Check it on the [Oracle Cloud Console]({0}/listing/{1}/{2}?region={3})', env.OCI_PUBLISHER_BASE_URL, env.LISTING_OCID, env.DRAFT_REVISION_ID, vars.OCI_CLI_REGION) || '' }}
-          ${{ inputs.release_to_marketplace && 'Publish it from there manually once it is approved' || '' }}
+          ${{ inputs.release_to_marketplace && '✅ Draft revision created, package added, and submitted for publishing.' || '' }}
+          ${{ inputs.release_to_marketplace && 'The new package is in the **Publish in Progress** stage - no manual action required.' || '' }}
+          ${{ inputs.release_to_marketplace && format('Track it on the [Oracle Cloud Console]({0}/listing/{1}/{2}?region={3})', env.OCI_PUBLISHER_BASE_URL, env.LISTING_OCID, env.DRAFT_REVISION_ID, vars.OCI_CLI_REGION) || '' }}
 
           ${{ ( ! inputs.release_to_marketplace && inputs.image_source_type == 'QCOW2 file URL' ) && '❌ **Marketplace release was not requested** (only Compute Image import and Object Storage upload performed)' || '' }}
           ${{ ( ! inputs.release_to_marketplace && inputs.image_source_type == 'Compute Image OCID' ) && '❌ **Marketplace release was not requested** (only image data resolution performed)' || '' }}

.github/workflows/scheduled-builds.yml

@@ -14,9 +14,10 @@ run-name: >-
 # publishing - a scheduled firing is a real release cycle: AWS releases
 # AMIs to all regions + Marketplace + wiki PR, Vagrant publishes boxes to
 # HCP, Azure releases to the gallery and creates Marketplace drafts, OCI
-# creates a Compute Image and submits a Marketplace draft for review
-# (Azure/OCI Live publishing stays manual). Tests gate publishing inside
-# each workflow. gcp-build-test-publish.yml is deliberately NOT scheduled.
+# creates a Compute Image and submits a Marketplace revision for
+# publishing (only Azure Live publishing stays manual). Tests gate
+# publishing inside each workflow. gcp-build-test-publish.yml is
+# deliberately NOT scheduled.
 #
 # Version quirks handled in the dispatch step:
 #   - aws-build-test-copy-release.yml spells Kitten 'kitten_10' (translated)

OCI_BUILD_RELEASE_TEST_PUBLISH.md

@@ -13,7 +13,7 @@ OCI image lifecycle in a single `workflow_dispatch`:
 3. **Test** every Compute Image (launch a fresh instance, assert
    release / arch / RPMs / disk / `dnf`).
 4. **Publish to Listings**: publish every image that passed its test to
-   the OCI Marketplace as a draft listing revision, submitted for review.
+   the OCI Marketplace as a draft listing revision, submitted for publishing.
 
 It reuses the same composite actions the standalone OCI workflows are
 built from, so behaviour matches them stage-for-stage. The standalone
@@ -49,7 +49,7 @@ qcow2 re-download.
 | `store_as_artifact` | `false` | Upload images as workflow artifacts. |
 | `upload_to_s3` | `true` | Still uploads to S3 in parallel; the compute-image stage no longer depends on it. |
 | `create_compute_image` | `true` | **Master gate** for stages 2-4. `false` = build-only run. |
-| `release_to_marketplace` | `true` | Release the image to the Marketplace listing (draft revision, submitted for review). |
+| `release_to_marketplace` | `true` | Release the image to the Marketplace listing (draft revision, submitted for publishing). |
 | `notify_mattermost` | `true` | Post per-stage notifications to Mattermost. |
 
 ### Stage gating
@@ -136,11 +136,12 @@ first and falls back to `dnf` so it works on the EL9 aarch64 runner.
   (this is the key difference from the Azure unified workflow, where
   aarch64 and aarch64-64k share one offer and must serialise).
 - The aarch64 + major-10 listing is matched as `AArch64/ARM64`.
-- Publishing to **Live is always manual** in the Oracle Cloud Console,
-  even after a successful review submission. The workflow leaves a draft
-  revision submitted for review; publish it from the Console once Oracle
-  approves. See [OCI_MARKETPLACE.md](OCI_MARKETPLACE.md) for the
-  listing / terms / artifact flow in detail.
+- The workflow submits the draft revision for publishing: the new package
+  lands in the **Publish in Progress** stage and Oracle carries it to Live -
+  no manual action in the Console is required. Publishing the new revision
+  automatically unpublishes the previous one. See
+  [OCI_MARKETPLACE.md](OCI_MARKETPLACE.md) for the listing / terms /
+  artifact flow in detail.
 
 ## Required GitHub Configuration
 

OCI_MARKETPLACE.md

@@ -241,7 +241,7 @@ graph TD
     WC --> UD[Update Draft Version Details]
     UD --> UN[Unset Default on Old Packages]
     UN --> NP[Create New Package as Default]
-    NP --> SB[Submit Draft for Review]
+    NP --> SB[Submit Draft for Publishing]
     SB --> S
     S --> MM[Send Mattermost Notification]
 ```
@@ -305,14 +305,13 @@ When the source type is `Artifact OCID`, artifact creation is skipped entirely 
 2. **Update** the draft's version details (version number, release date, release notes link), headline, and tagline
 3. **Unset default** on any existing default packages in the draft
 4. **Create** a new package as default (linking artifact + terms + version)
-5. **Submit** the draft for Oracle review
+5. **Submit** the draft for publishing
 
-After Oracle approves the revision, it must be **published manually** from the OCI Console. Publishing the new revision automatically unpublishes the previous one.
+Submitting moves the new package to the **Publish in Progress** stage; Oracle carries it to Live with no manual action required. Publishing the new revision automatically unpublishes the previous one.
 
-## Manual Steps After Workflow Completes
+## After the Workflow Completes
 
-1. **Wait for Oracle to approve** the submitted revision (check status in OCI Console)
-2. **Publish** the approved revision from the [OCI Publisher Console](https://cloud.oracle.com/publisher) — the previous revision is automatically unpublished
+No manual steps are required: the new package is in the **Publish in Progress** stage. Track it in the [OCI Publisher Console](https://cloud.oracle.com/publisher); once it goes Live, the previous revision is automatically unpublished.
 
 ## Testing
 

SCHEDULED_BUILDS.md

@@ -14,10 +14,10 @@ version-aware `run-name` works natively for scheduled runs.
 > runs the FULL pipeline, publishing included: AWS releases AMIs to all
 > regions + Marketplace + a wiki PR, Vagrant publishes boxes to HCP, Azure
 > releases to the Compute Gallery and creates Marketplace drafts, OCI
-> creates a Compute Image and submits a Marketplace draft for review
-> (Azure/OCI Live publishing stays manual). Tests gate publishing inside
-> each workflow. `gcp-build-test-publish.yml` is deliberately NOT
-> scheduled.
+> creates a Compute Image and submits a Marketplace revision for
+> publishing (only Azure Live publishing stays manual). Tests gate
+> publishing inside each workflow. `gcp-build-test-publish.yml` is
+> deliberately NOT scheduled.
 
 ## The schedule