azure-pipelines-tasks-terraform
azure-pipelines-tasks-terraform copied to clipboard
[Question] Release Notes 1.2.3
Hey there,
I'm currently looking into an issue related to az login within the TerraformCLI Azure DevOps task and passwords stating with a dash. That issue was fixed around 6 month ago and released in 1.2.1.
I'm still facing the issue and so looking into it.
I do not expect that the change was reverted in 1.2.3 since its still in the code of the main and not changed over the last 6 month but I don't find the GitHub release for 1.2.3 and was wondering where else I could find the release notes 🙂 I also didn't find any release action or something
Update: when reading the comment again...
It is published already in
@2in the extension. It could be a little while before this migrates to@1Maybe thats my issue. Got an idea when its migrated to@1?
How does the versioning work here exactly?
I use @1 and the task says when its running it is version 1.2.3
It was indeed reverted because it broke all the unit tests. I was waiting for a version which fixed the issue and fixed the tests.
Hey @jason-johnson , oh ye I somehow missed that, sorry. It was implemented, then reverted and then added again 8 month ago and tagged as 1.2.2.
The task in my pipeline run does say 1.2.3. Was it reverted again or how does the versioning work? Since in some comment you said something about @1 vs @2.
Update: Ah well yes, that's why I asked about notes for 1.2.3 and how the versioning works, since from my understanding it should be in the code again since 1.2.2
@1 means the highest version of the 1 tag. @2 means the latest merged code.
@jason-johnson thanks, understood.
But when my pipeline run says Version 1.2.3 shouldn't it then be fixed since you added it back in tag 1.2.2 - https://github.com/jason-johnson/azure-pipelines-tasks-terraform/releases/tag/1.2.2
There seems to be no GitHub tag / release for 1.2.3 but in Azure DevOps it exists.
Just trying to understand 🙂
The version is created by GoReleaser which may be bumping the version after the tag.