Skip to content

chore(main): release 0.8.0 #43

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

Merged
merged 1 commit into from
Jun 17, 2025
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 13, 2025

🤖 I have created a release beep boop

0.8.0 (2025-06-17)

Features

  • INT-83: dial in configs for tflint (#39) (60c58f4)

Bug Fixes

  • gha-trunk-upgrade: wait for checks and merge with admin (#42) (0c399bc)
  • gha: use app–generated token to create release-please PRs (#45) (a0c0d46)
  • linter configs to root folder (#44) (7aacf9f)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner June 13, 2025 18:29
Gowiem pushed a commit that referenced this pull request Jun 16, 2025
## what

- Configure release-please workflow to create PRs using an App–generated
token istead of GITHUB_TOKEN.

## why

- When use the repository’s GITHUB_TOKEN to perform tasks on behalf of
the GitHub Actions app (the github-actions[bot]), events triggered by
that token will not create new workflow runs, with the sole exceptions
of workflow_dispatch and repository_dispatch. This is an intentional
safeguard to avoid accidental infinite loops of workflows triggering
themselves

[github.com](https://github.com/orgs/community/discussions/26875?utm_source=chatgpt.com).

- Pull requests created programmatically by the github-actions[bot]
(i.e., using GITHUB_TOKEN) do not fire the pull_request event, so any
workflow with on: pull_request will not start. Even though the PR
appears normally, downstream checks see no trigger and remain stuck, see
#43

## references

-
https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication
- https://github.com/orgs/community/discussions/26875


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated the release workflow to use a GitHub App token for
authentication during the release process.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@masterpointbot masterpointbot bot force-pushed the release-please--branches--main branch 2 times, most recently from ca37d85 to 5bfae9e Compare June 17, 2025 13:16
@masterpointbot masterpointbot bot force-pushed the release-please--branches--main branch from 5bfae9e to 6184212 Compare June 17, 2025 15:00
@gberenice gberenice merged commit 36ac094 into main Jun 17, 2025
5 checks passed
@gberenice gberenice deleted the release-please--branches--main branch June 17, 2025 15:05
@masterpointbot
Copy link
Contributor

🤖 Created releases:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant