Skip to content

chore(ci): fix semantic-release to use github app #756

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
Jul 30, 2025

Conversation

grdsdev
Copy link
Collaborator

@grdsdev grdsdev commented Jul 29, 2025

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 16602068930

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 77.977%

Totals Coverage Status
Change from base Build 16598967050: 0.0%
Covered Lines: 5403
Relevant Lines: 6929

💛 - Coveralls

@grdsdev grdsdev requested a review from staaldraad July 29, 2025 17:53
@grdsdev grdsdev enabled auto-merge (squash) July 30, 2025 08:28
@grdsdev grdsdev merged commit 81ee6dd into main Jul 30, 2025
17 checks passed
@grdsdev grdsdev deleted the fix/semantic-release branch July 30, 2025 08:46
@supabase-releaser
Copy link

🎉 This PR is included in version 2.31.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants