Skip to content

ci: switch release automation from semantic-release to release-please - #33

Open
stuartp44 wants to merge 1 commit into
mainfrom
stu/switch_to_release_please
Open

ci: switch release automation from semantic-release to release-please#33
stuartp44 wants to merge 1 commit into
mainfrom
stu/switch_to_release_please

Conversation

@stuartp44

@stuartp44 stuartp44 commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Replace python-semantic-release with googleapis/release-please-action so releases go through a standing release pull request instead of being published directly on push to main. Release Please updates the version in custom_components/minibrew/manifest.json and CHANGELOG.md in the PR; merging it tags the commit and publishes the GitHub release.

  • Add release-please-config.json and .release-please-manifest.json (seeded at 0.11.0 to match the latest tag)
  • Update .github/workflows/release.yml to run release-please after the existing HACS/hassfest/manifest/commitlint validation jobs
  • Remove pyproject.toml (semantic-release-only config)
  • Drop the now-unused pip ecosystem from .github/dependabot.yml and the semantic-release prompt from scripts/setup-dev.sh
  • Update .github/COPILOT_INSTRUCTIONS.md and .github/RELEASE_WORKFLOWS.md to describe the new release-PR workflow

Description

Type of Change

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Code style changes (formatting, missing semi-colons, etc)
  • refactor: Code refactoring
  • perf: Performance improvements
  • test: Adding or updating tests
  • build: Changes to build system or dependencies
  • ci: Changes to CI configuration
  • chore: Other changes that don't modify src or test files

Changes Made

Testing

  • Tested with MiniBrew Craft device
  • Tested with MiniBrew Keg device
  • Tested in Home Assistant
  • Verified sensors update correctly

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • My commit messages follow the Conventional Commits specification
  • PR title follows the Conventional Commits format (e.g., feat: add new sensor)
  • I have updated the documentation accordingly
  • My changes generate no new warnings

Breaking Changes

  • This PR contains breaking changes

Preview Release

To create a preview release for testing:

  • Add the preview-release label to this PR, OR
  • Comment /preview-release on this PR

A draft release will be automatically created that you can share for testing.

Related Issues

Closes #

Replace python-semantic-release with googleapis/release-please-action
so releases go through a standing release pull request instead of
being published directly on push to main. Release Please updates the
version in custom_components/minibrew/manifest.json and
CHANGELOG.md in the PR; merging it tags the commit and publishes the
GitHub release.

- Add release-please-config.json and .release-please-manifest.json
  (seeded at 0.11.0 to match the latest tag)
- Update .github/workflows/release.yml to run release-please after
  the existing HACS/hassfest/manifest/commitlint validation jobs
- Remove pyproject.toml (semantic-release-only config)
- Drop the now-unused pip ecosystem from .github/dependabot.yml and
  the semantic-release prompt from scripts/setup-dev.sh
- Update .github/COPILOT_INSTRUCTIONS.md and
  .github/RELEASE_WORKFLOWS.md to describe the new release-PR workflow

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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