From c000725551fbb9ca82877eb3890622e622432f8b Mon Sep 17 00:00:00 2001
From: George Claireaux <george@claireaux.co.uk>
Date: Thu, 7 Apr 2022 10:53:09 -0700
Subject: [PATCH] clarity on version bump with /publish

---
 .github/pull_request_template.md     | 4 +---
 docs/connector-development/README.md | 4 ++--
 2 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 7b1083c48396d..102105214f584 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -68,9 +68,7 @@ If this is a community PR, the Airbyte engineer reviewing this PR is responsible
 - [ ] Build is successful
 - [ ] If new credentials are required for use in CI, add them to GSM. [Instructions](https://docs.airbyte.io/connector-development#using-credentials-in-ci).
 - [ ] [`/test connector=connectors/<name>` command](https://docs.airbyte.io/connector-development#updating-an-existing-connector) is passing
-- [ ] New Connector version released on Dockerhub by running the `/publish` command described [here](https://docs.airbyte.io/connector-development#updating-an-existing-connector)
-- [ ] After the new connector version is published, connector version bumped in the seed directory as described [here](https://docs.airbyte.io/connector-development#publishing-a-connector)
-- [ ] Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described [here](https://docs.airbyte.io/connector-development#publishing-a-connector)
+- [ ] New Connector version released on Dockerhub and connector version bumped by running the `/publish` command described [here](https://docs.airbyte.io/connector-development#updating-an-existing-connector)
 
 </details>
 
diff --git a/docs/connector-development/README.md b/docs/connector-development/README.md
index 96f134f30028a..11a096d53b60c 100644
--- a/docs/connector-development/README.md
+++ b/docs/connector-development/README.md
@@ -124,8 +124,8 @@ Once you've finished iterating on the changes to a connector as specified in its
    /publish connector=(connectors|bases)/<connector_name>
    ```
    
-4. OPTIONAL: Only necessary if the automated connector version bump fails
-   * Update the connector definition in the Airbyte connector index to use the new version:
+4. OPTIONAL: Necessary if this is a new connector, or the automated connector version bump fails
+   * Update/Add the connector definition in the Airbyte connector index to use the new version:
         * `airbyte-config/init/src/main/resources/seed/source_definitions.yaml` if it is a source
         * `airbyte-config/init/src/main/resources/seed/destination_definitions.yaml` if it is a destination.