Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency suzuki-shunsuke/github-comment to v6.3.2 #371

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 13, 2025

This PR contains the following updates:

Package Update Change
suzuki-shunsuke/github-comment minor v6.2.0 -> v6.3.2

Release Notes

suzuki-shunsuke/github-comment (suzuki-shunsuke/github-comment)

v6.3.2

Compare Source

Pull Requests | Issues | suzuki-shunsuke/github-comment@v6.3.1...v6.3.2

v6.3.1

Compare Source

Pull Requests | Issues | suzuki-shunsuke/github-comment@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.json

Others

#​1704 Publish JSON Schema for github-comment's configuration files

v6.3.0

Compare Source

Pull Requests | Issues | suzuki-shunsuke/github-comment@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 test

You can post both GitHub and a file.

e.g.

github-comment exec -out github -out "file:$GITHUB_STEP_SUMMARY" -- npm test

The 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.2.1

Compare Source

Pull Requests | Issues | suzuki-shunsuke/github-comment@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.yaml

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Feb 13, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v6.3.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/suzuki-shunsuke-github-comment-6.x branch February 13, 2025 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant