v4.0.1

Pull Requests | Issues | v4.0.0...v4.0.1

Others

#580 Release SLSA Provenance and sign checksum files by Cosign
#580 Update Go from 1.19.1 to 1.19.4
#581 Update go-github from v43 to v49

v4.0.1-0

v4.0.0...v4.0.1-0

#580

v4.0.0

Pull Requests | Issues | v3.4.2...v4.0.0

⚠️ Breaking Changes ⚠️

#378 Remove features to output environment variables for security

• Some template functions are removed: expandenv, env, getHostByName
  • http://masterminds.github.io/sprig/os.html
  • http://masterminds.github.io/sprig/network.html
• configuration ci is removed

How to migrate

• Use the -var option instead of env
• tfcmt supports Google Cloud Build, so you don't have to use the configuration ci to support Google Cloud Build
• tfactioin >= v0.5.13 supports tfcmt v4.0.0 ref

v4.0.0-4

Pull Requests | Issues | v4.0.0-3...v4.0.0-4

Bug Fixes

#451 Get an associated pull request number before adding pull request labels

Problem to solve

https://github.com/suzuki-shunsuke/tfcmt/blob/fc4a6c08b78b0b240c6a1d340f8c9a23807101a1/pkg/notifier/github/plan.go#L31-L33

Labels aren't set, because PR.IsNumber() is false.

tfcmt should get an associated pull request before adding pull request labels.

v3.4.2

Pull Requests | Issues | v3.4.1...v3.4.2

Bug Fixes

#451 Add pull request labels properly even if a pull request number isn't passed as an argument or an environment variable

tfcmt plan gets an associated pull request from a commit hash if a pull request number isn't passed as an argument or an environment variable,
and adds pull request labels according to the terraform plan result.
This update has fixed a bug that a pull request label isn't added properly.

If a pull request number is passed as an argument or an environment variable, this update isn't related.

v4.0.0-3

Pull Requests | Issues | v4.0.0-2...v4.0.0-3

Changelog

• 04346bd Merge branch 'main' into fix/prevent-output-env-2

v3.4.1

Pull Requests | Issues | v3.4.0...v3.4.1

Bug Fixes

#436 Fix links to GitHub Actions jobs in GitHub Enterprise

Others

#437 Update Go from v1.18.5 to v1.19.1

Contributors

Thank you, Contributors!

@Warashi #436
@hirosassa #412

v3.4.1-0

Pull Requests | Issues | v3.4.0...v3.4.1-0

Bug Fixes

#436 Fix links to GitHub Actions jobs in GitHub Enterprise

Others

#437 Update Go from v1.18.5 to v1.19.1

Contributors

Thank you, Contributors!

@Warashi #436
@hirosassa #412

v4.0.0-2

Pull Requests | Issues | v4.0.0-1...v4.0.0-2

Changelog

• 9475165 Merge branch 'main' into fix/prevent-output-env-2

v3.4.0

Pull Requests | Issues | v3.3.0...v3.4.0

Features

#387 #390 Create comments to pull request instead of commit

GitHub no longer shows commit comments in the pull request timeline ¹.

From v3.4.0, tfcmt gets an associated pull request from commit hash and creates a comment to not commit but associated pull request.
If there is no associated pull request, tfcmt sends a comment to commit.

Example

$ tfcmt -v
tfcmt version 3.4.0-1 (48333cac413f4500b2631eebb9703a9edc5e0a9d)

$ terraform -v
Terraform v1.2.6
on darwin_arm64
+ provider registry.terraform.io/hashicorp/null v3.1.1

export GITHUB_TOKEN=xxx
export CIRCLECI=true
export CIRCLE_PROJECT_USERNAME=suzuki-shunsuke
export CIRCLE_PROJECT_REPONAME=test-github-action
export CIRCLE_SHA1=092cda867dea7b7a229bc2dcff64aaba8fb26f8d

suzuki-shunsuke/test-github-action@092cda8

$ tfcmt plan -- terraform plan
null_resource.foo: Refreshing state... [id=8966706083595703589]
null_resource.bar: Refreshing state... [id=7780302426904623778]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

👍 tfcmt v3.4.0 creates a pull request comment.

suzuki-shunsuke/test-github-action#104 (comment)

On the other hand, tfcmt v3.3.0 creates a commit comment.

suzuki-shunsuke/test-github-action@092cda8#commitcomment-80523712

Others

#392 Update Go from v1.18.4 to v1.18.5

Contributors

Thank you, Contributors!

@micnncim #387 #390

1. https://github.blog/changelog/2022-08-04-commit-comments-no-longer-appear-in-the-pull-request-timeline/ ↩