Skip to content

chore: automate releases with release-please action#396

Merged
marcossevilla merged 8 commits intomainfrom
chore/release-please-workflow
Nov 26, 2025
Merged

chore: automate releases with release-please action#396
marcossevilla merged 8 commits intomainfrom
chore/release-please-workflow

Conversation

@Josh-Sanford
Copy link
Contributor

@Josh-Sanford Josh-Sanford commented Nov 20, 2025

Status

READY

Description

Add release-please workflow using the release-please Github action to automate releases.

Example PR:

Example release:

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@Josh-Sanford Josh-Sanford changed the title automate releases with release please action chore: automate releases with release please action Nov 20, 2025
@Josh-Sanford Josh-Sanford marked this pull request as ready for review November 20, 2025 19:44
@Josh-Sanford Josh-Sanford requested a review from a team as a code owner November 20, 2025 19:44
@Josh-Sanford Josh-Sanford changed the title chore: automate releases with release please action chore: automate releases with release-please action Nov 21, 2025
Copy link
Contributor

@matiasleyba matiasleyba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job, just a couple of notes from me:

  • I think we should remove the scripts from /tool
  • It would be great to update the CONTRIBUTING.md to reflect the changes in the release process, see an example here.
  • The changelog seems to be malformed, version 2.0.0 is below 1.x. You can fix this by adding a #Changelog header to the file. See this as an example.
  • I believe that not all paths should be considered for release.
    For example, in my opinion, /site should be ignored.
    Here is an example of how to ignore paths.
    Please review the other paths to see which ones we should include or not.

Let me know if you have any questions, thanks for contributing.

@omartinma
Copy link
Contributor

@Josh-Sanford issue about bloc lint has been fixed so i believe we should be able to revert some of the changes

@Josh-Sanford Josh-Sanford force-pushed the chore/release-please-workflow branch from 63b549d to 5230ccf Compare November 21, 2025 18:37
Adds a GitHub Actions workflow to automate releases using release-please.
The workflow runs on pushes to main and can be triggered manually.
Adds release-please configuration with changelog sections and
pull request settings. Initializes manifest with version 1.18.0.
@Josh-Sanford Josh-Sanford force-pushed the chore/release-please-workflow branch from 5230ccf to 731e015 Compare November 21, 2025 18:44
@marcossevilla marcossevilla merged commit 0b293a8 into main Nov 26, 2025
8 checks passed
@marcossevilla marcossevilla deleted the chore/release-please-workflow branch November 26, 2025 14:34
@vgvbot vgvbot mentioned this pull request Nov 26, 2025
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.

5 participants