Set version to 3.6.0

Author: engswee

.github/workflows/go-prod.yml

@@ -102,5 +102,5 @@ jobs:
         file: ./build/Dockerfile
         push: true
         tags: |
-          engswee/flashpipe:3.5.1
+          engswee/flashpipe:3.6.0
           engswee/flashpipe:latest

.github/workflows/go-qa.yml

@@ -102,5 +102,5 @@ jobs:
         file: ./build/Dockerfile
         push: true
         tags: |
-          engswee/cpi-cicd:3.5.1
+          engswee/cpi-cicd:3.6.0
           engswee/cpi-cicd:latest

docs/documentation.md

@@ -27,15 +27,15 @@ Technically, it should be possible to use _FlashPipe_ on any CI/CD platform that
 With major release `3.0.0`, _FlashPipe_ returns to the simpler approach of having a single tag for each version release. Separate full and lite tags are no longer available.
 The latest Docker image for _FlashPipe_ is
 
-  `engswee/flashpipe:3.5.1`
+  `engswee/flashpipe:3.6.0`
 
 For a list of all available images tags, check [here](https://hub.docker.com/r/engswee/flashpipe/tags).
 
 ### Rolling tags
 Starting from version `3.0.0`, rolling tag `latest` is introduced to make it easier to get the latest version. This rolling tag is dynamic and will point to the latest version of the image.
 
 ### Usage recommendation
-- When using _FlashPipe_ in productive pipelines, use an immutable tag (e.g. `3.5.1`) to ensure stability so that the pipeline will not be affected negatively by new version releases.
+- When using _FlashPipe_ in productive pipelines, use an immutable tag (e.g. `3.6.0`) to ensure stability so that the pipeline will not be affected negatively by new version releases.
 - When using _FlashPipe_ in development pipelines, use rolling tag `latest` to always get the latest version.
 
 ## Authentication

internal/cmd/root.go

@@ -14,7 +14,7 @@ import (
 )
 
 func NewCmdRoot() *cobra.Command {
-	var version = "3.5.1" // FLASHPIPE_VERSION
+	var version = "3.6.0" // FLASHPIPE_VERSION
 
 	// rootCmd represents the base command when called without any subcommands
 	rootCmd := &cobra.Command{