updating release docs

Author: abottchen

README.md

@@ -9,19 +9,18 @@ To run tests (from root of repo):
 
 1. Create a branch off `master` using the following convention:
 ```shell
-git checkout -b 1.6.0-release
+git checkout -b 1.7.0-release
 ```
 2. On a new branch based on the release branch, update CHANGELOG.md with any changes in this release and metadata.json with the new version number.
 3. Commit these changes and put up a PR against the release branch you created in Step 1 and get review.
 4. Once the changes have been approved and merged to the release branch, pull down the updated release branch and tag the module.
 ```shell
-git tag -a 1.6.0 -m "1.6.0"
+git tag -a 1.7.0 -m "1.7.0"
 ```
-6. Run `pdk build --force` in the root of the module to get the new tarball. The `force` flag is required because this module is not fully compatible with modern PDK versions, and we don't want the PDK to attempt to convert anything. This is the same thing we do with the `cd4peadm` module.
-7. Log into https://forge.puppet.com as 'puppetlabs' and publish the new module version
-8. Update the ref in PE: https://github.com/puppetlabs/pe-tasks-vanagon/blob/main/configs/components/puppetlabs-cd4pe_jobs.json. This will ensure that the new version is shipped with the next PE release.
-9. Push your new tag up to the repo
+6. Run the https://github.com/puppetlabs/PipelinesInfra/actions/workflows/release-cd4pe_jobs.yml workflow with the release branch created above to build the tarball and push it to the forge.
+7. Update the ref in PE: https://github.com/puppetlabs/pe-tasks-vanagon/blob/main/configs/components/puppetlabs-cd4pe_jobs.json. This will ensure that the new version is shipped with the next PE release.
+8. Push your new tag up to the repo
 ```shell
 git push --tags
 ```
-10. Make a PR from the release branch back to `master`. Once this is merged the release branch should be deleted.
+9. Make a PR from the release branch back to `master`. Once this is merged the release branch should be deleted.