Prepare 0.6.0 (#69)

* Prepare 0.6.0

* add bitbucket pipes releasing docs

Author: atrakh

CHANGELOG.md

@@ -2,8 +2,7 @@
 
 All notable changes to the ld-find-code-refs program will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
 
-## Master
-
+## [0.6.0] - 2019-02-11
 ### Added
 - Added a new command line argument, `version`. If provided, the current `ld-find-code-refs` version number will be logged, and the scanner will exit with a return code of 0.
 - The `debug` option is now available to the CircleCI orb.

RELEASING.md

@@ -1,14 +1,16 @@
 # Releasing
 
 ## Versioning
-This project adheres to [Semantic Versioning](http://semver.org). Release version tags should be in the form `MAJOR.MINOR.PATCH`, with no leading v. When releasing, be sure to update the version number in [`version.go`](https://github.com/launchdarkly/ld-find-code-refs/blob/master/internal/version/version.go)
+This project adheres to [Semantic Versioning](http://semver.org). Release version tags should be in the form `MAJOR.MINOR.PATCH`, with no leading v. When releasing, be sure to update the version number in [`version.go`](https://github.com/launchdarkly/ld-find-code-refs/blob/master/internal/version/version.go), and in the [CircleCI orb](https://github.com/launchdarkly/ld-find-code-refs/blob/master/build/package/circleci/orb.yml).
 
 ## Github Releases
 
 This project uses [goreleaser](https://goreleaser.com/) to generate github releases. Releases are automated via CircleCI. To generate a new release, simply tag the commit you want to release and push the tag. If the tag ends in -rc(.+), the github release will be marked as "Pre-release." If you'd like to see how release notes are generated, see the .circleci/config.yml publish job.
 
 Make sure you update the changelog before generating a release.
 
+Once a release has been completed, update the [BitBucket pipelines](https://bitbucket.org/launchdarkly/ld-find-code-refs-pipe) repo with the new version number, and push a tag containing the version number along with your commit. Example release commit: https://bitbucket.org/launchdarkly/ld-find-code-refs-pipe/commits/0b1e920c7322cd495f4fc1a09d339342d32606e4
+
 ## Docker Hub
 
 To push a new image version to Docker hub, run `make publish-cli-docker TAG=$VERSION` or `make publish-github-actions-docker TAG=$VERSION`, where `$VERSION` is the version you want to release. This will compile the ld-find-code-refs binary for either the base command line code ref finder or the github actions specialized finder, build a new image with your version tagged, and also point latest at that tag and push both latest and $VERSION to docker hub.

build/package/circleci/orb.yml

@@ -7,7 +7,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@0.5.0
+        launchdarkly: launchdarkly/ld-find-code-refs@0.6.0
       workflows:
         main:
           jobs:
@@ -21,7 +21,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@0.5.0
+        launchdarkly: launchdarkly/ld-find-code-refs@0.6.0
       workflows:
         main:
           jobs:
@@ -36,7 +36,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@0.5.0
+        launchdarkly: launchdarkly/ld-find-code-refs@0.6.0
       workflows:
         main:
           jobs:
@@ -52,7 +52,7 @@ examples:
     usage:
       version: 2.1
       orbs:
-        launchdarkly: launchdarkly/ld-find-code-refs@0.5.0
+        launchdarkly: launchdarkly/ld-find-code-refs@0.6.0
       workflows:
         main:
           jobs:
@@ -113,7 +113,7 @@ jobs:
         type: boolean
         default: false
     docker:
-      - image: launchdarkly/ld-find-code-refs:0.5.0
+      - image: launchdarkly/ld-find-code-refs:0.6.0
     steps:
       - checkout:
           path: /repo

internal/version/version.go

@@ -1,3 +1,3 @@
 package version
 
-const Version = "0.5.0"
+const Version = "0.6.0"