Update references to 0.9.0

inviqa · Aug 12, 2020 · 9d42f2d · 9d42f2d
1 parent e1750b7
commit 9d42f2d
Show file tree

Hide file tree

Showing 9 changed files with 11 additions and 11 deletions.
diff --git a/README.md b/README.md
@@ -92,15 +92,15 @@ The [deploy script](./deploy) does a similar thing but the end result is output
 committed as a publish commit to a temporary build branch.
 
 A "subtree-split" is then performed which outputs a directory for each folder into a "publish" folder, where it is then
-force pushed to the individual harness repositories' `0.8.x` branch.
+force pushed to the individual harness repositories' `0.9.x` branch.
 
 ## Release
 
 ### Changelog Generation
 
 We are keeping a changelog, powered by [GitHub Changelog Generator].
 
-When ready to tag a release, make a new branch from the `0.8.x` branch for the changelog entries:
+When ready to tag a release, make a new branch from the `0.9.x` branch for the changelog entries:
 1. Generate a `repo` scope token for use with the changelog generator: https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token
 2. Export it in your environment: `export CHANGELOG_GITHUB_TOKEN=...`
 3. Run the following docker command to generate the changelog, replacing `<nextReleaseTag>` with the version number you
@@ -125,7 +125,7 @@ Once the CHANGELOG.markdown is in the branch you wish to release:
 3. Verify you don't have any ignored files in `src/`, and clean up if you do: `git status --ignored`
 4. Run the deploy script: `./deploy`
 5. On each downstream repository:
-   1. Tag the latest `0.8.x` branch push as the release version.
+   1. Tag the latest `0.9.x` branch push as the release version.
    2. Push the tag to the repository
 6. Submit a pull request to [my127/my127.io] which adds the new release version and asset download URL for the
    php-based harnesses to `harnesses.json`

diff --git a/src/_base/README.md b/src/_base/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/php:v0.8.0`
+2. Run `ws create <projectName> inviqa/php:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/akeneo/README.md b/src/akeneo/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/akeneo:v0.8.0`
+2. Run `ws create <projectName> inviqa/akeneo:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/drupal8/README.md b/src/drupal8/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/drupal8:v0.8.0`
+2. Run `ws create <projectName> inviqa/drupal8:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/magento1/README.md b/src/magento1/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/magento1:v0.8.0`
+2. Run `ws create <projectName> inviqa/magento1:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/magento2/README.md b/src/magento2/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/magento2:v0.8.0`
+2. Run `ws create <projectName> inviqa/magento2:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/spryker/README.md b/src/spryker/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/spryker:v0.8.0`
+2. Run `ws create <projectName> inviqa/spryker:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/symfony/README.md b/src/symfony/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/symfony:v0.8.0`
+2. Run `ws create <projectName> inviqa/symfony:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git:

diff --git a/src/wordpress/README.md b/src/wordpress/README.md
@@ -3,7 +3,7 @@
 To use this harness:
 
 1. Install [Workspace]
-2. Run `ws create <projectName> inviqa/wordpress:v0.8.0`
+2. Run `ws create <projectName> inviqa/wordpress:v0.9.0`
 3. Fill in project-specific AWS and Github credentials, set as blank if you don't need them
 4. Change to the <projectName> directory: `cd <projectName>`
 5. Create an initial commit, ensuring that `workspace.override.yml` is not added to git: