Releases: suzuki-shunsuke/github-comment
v6.3.3
Pull Requests | Issues | v6.3.2...v6.3.3
#2015 Update Go to v1.24.5
#2015 Release SBOM
#2015 Add license files of Go and Go Modules to released assets
v6.3.3-0
365671fv6.3.2
v6.3.1
Pull Requests | Issues | v6.3.0...v6.3.1
Features
#1705 init: Improve the configuration generated by init command
Add a code comment for YAML Language Server
# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/github-comment/main/json-schema/github-comment.jsonOthers
#1704 Publish JSON Schema for github-comment's configuration files
v6.3.1-0
839adcav6.3.0
Pull Requests | Issues | v6.2.1...v6.3.0
Features
#1566 exec: Add the option -out to output the result to text files
https://suzuki-shunsuke.github.io/github-comment/output-file
Instead of posting a comment to a GitHub Issue or Pull Request, you can output the result to a text file using github-comment exec's -out option.
This is useful to output the result of GitHub Actions workflow_dispatch or schedule events to $GITHUB_STEP_SUMMARY.
e.g.
github-comment exec -out "file:$GITHUB_STEP_SUMMARY" -- npm testYou can post both GitHub and a file.
e.g.
github-comment exec -out github -out "file:$GITHUB_STEP_SUMMARY" -- npm testThe value of -out must be either github or file:<file path>.
If a given file doesn't exist, the file is created.
Otherwise, the content is appended.
v6.3.0-1
deb78caPull Requests | Issues | v6.2.1...v6.3.0-1
Changelog
- deb78ca chore: update cmdx tasks
- ec11f8c chore(deps): update dependency aquaproj/aqua-registry to v4.230.0 (#1567)
- 8b6e781 feat(exec): support the option -out (#1566)
- 0832d9d chore(deps): update dependency suzuki-shunsuke/ghalint to v1 (#1562)
- 54ce4b5 fix(deps): update module github.com/google/go-github/v65 to v66 (#1565)
- 7e59569 chore(deps): update dependency aquaproj/aqua-registry to v4.229.0 (#1563)
- 99e139b fix(deps): update module golang.org/x/term to v0.25.0 8000 (#1561)
v6.2.1
Pull Requests | Issues | v6.2.0...v6.2.1
Others
#1560 Update Go to 1.23.2
#1545 Create GitHub Artifact Attestations
https://github.com/suzuki-shunsuke/github-comment/attestations
You can verify downloaded assets from GitHub Releases using GitHub CLI.
gh release download -R suzuki-shunsuke/github-comment v6.2.1 -p github-comment_6.2.1_darwin_arm64.tar.gz
gh attestation verify github-comment_6.2.1_darwin_arm64.tar.gz \
-R suzuki-shunsuke/github-comment \
--signer-workflow suzuki-shunsuke/go-release-workflow/.github/workflows/release.yamlv6.2.1-1
772610dv6.2.0
Pull Requests | Issues | v6.1.0...v6.2.0
Features
#1490 Get GitHub API endpoints from environment variables GITHUB_API_URL and GITHUB_GRAPHQL_URL
About these environment variables, please see the document.
- GitHub Enterprise Server: https://docs.github.com/en/enterprise-server@3.13/actions/writing-workflows/choosing-what-your-workflow-does/variables
- GitHub Enterprise Cloud: https://docs.github.com/en/enterprise-cloud@latest/actions/writing-workflows/choosing-what-your-workflow-does/variables
- GitHub (github.com): https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/variables
If you use GitHub Enterprise Server, you had to configure ghe_base_url and ghe_graphql_endpoint in the configuration file.
https://suzuki-shunsuke.github.io/github-comment/github-enterprise
From this release, github-comment gets these variables from environment variables GITHUB_API_URL and GITHUB_GRAPHQL_URL.
They are GitHub Actions' built in environment variables, so you don't have to set them in GitHub Actions.