Skip to content

fix: configure release-please for initial 0.2.0 release#7

Merged
mldangelo merged 1 commit intomainfrom
fix/release-please-config
Jan 6, 2026
Merged

fix: configure release-please for initial 0.2.0 release#7
mldangelo merged 1 commit intomainfrom
fix/release-please-config

Conversation

@mldangelo
Copy link
Member

Summary

Fixes the release-please workflow by adding the missing configuration and preparing for the first release (0.2.0).

Changes

  • Add release-please-config.json: Configures release-please for Python package management with automatic version bumping in pyproject.toml
  • Set version to 0.1.0: Updated both .release-please-manifest.json and pyproject.toml from 0.2.0 to 0.1.0

This allows release-please to create a release PR that will bump the version to 0.2.0 for the first actual release, rather than trying to release 0.2.1.

How it works

Once this PR is merged:

  1. Release-please will analyze commits since 0.1.0
  2. It will create a release PR bumping to 0.2.0 (based on the fix: and feat: commits)
  3. When that release PR is merged, it will:
    • Create a GitHub release with tag v0.2.0
    • Trigger the build and PyPI publish workflow
    • Automatically publish to PyPI using OIDC

Related Issues

Fixes #8

🤖 Generated with Claude Code

Add release-please configuration and set versions to 0.1.0 to enable
the first release PR to bump to 0.2.0. This fixes the workflow failure
caused by missing release-please-config.json.

Changes:
- Add release-please-config.json with Python package configuration
- Set .release-please-manifest.json to 0.1.0 (from 0.2.0)
- Set pyproject.toml version to 0.1.0 (from 0.2.0)

This allows release-please to create a PR that will bump the version
to 0.2.0 for the first actual release.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@mldangelo mldangelo merged commit d5c95f9 into main Jan 6, 2026
10 checks passed
@mldangelo mldangelo deleted the fix/release-please-config branch February 24, 2026 23:22
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