Fix for 1.6.x: Add vault revision to --version cmd#13445
Fix for 1.6.x: Add vault revision to --version cmd#13445mladlow merged 2 commits intorelease/1.6.xfrom
1.6.x: Add vault revision to --version cmd#13445Conversation
|
This pull request is being automatically deployed with Vercel (learn more). vault – ./website🔍 Inspect: https://vercel.com/hashicorp/vault/Biout3ULWuJEXapF35VPdQcC49Et [Deployment for 418498d canceled] vault-storybook – ./ui🔍 Inspect: https://vercel.com/hashicorp/vault-storybook/BXHzbtqPaXem4LHY7W2SHxwgtqq9 [Deployment for 418498d canceled] |
|
Do you know what's up with the pre-flight checks? |
|
I'm going to re-milestone this for 1.9.3. I'd like to merge it, but it doesn't need to happen this week. |
|
I'm taking a look now- edit: the .circleci/Makefile file was broken. I pushed up a fix for the makefile and then ran |
|
The other branches looked good - at least that check was passing. |
…ashicorp#13439) (hashicorp#13445) Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
The output of
./vault --versionchanged since Vault onboarded to CRT/GitHub Actions for building artifacts.This change adds back in the revision string to the version command. Output from the artifacts built on this branch: