Repository navigation
Release prep: 0.1.0 changelog and manually-triggerable releases - #31
Merged
Merged
Conversation
Everything to date ships as 0.1.0, so fold the Unreleased section into a dated release entry with the headliners (library API, MCP server, BM25 search, lean install) up top and the merge-order history below. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QVbxD1gd3gsC6zXKE6L3ya
A workflow_dispatch trigger with a tag_name input lets the release run be started from the Actions tab (or API) when a tag can't be pushed directly; softprops/action-gh-release creates the tag itself in that case. Tag-push releases behave exactly as before via github.ref_name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QVbxD1gd3gsC6zXKE6L3ya
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last PR before v0.1.0 ships. Two commits:
Changelog consolidated into the release entry
Everything built to date is 0.1.0, so the "Unreleased" section folds into a dated 0.1.0 — 2026-09-04 entry: headliners up top (library API with styled plots, MCP server, BM25 search with its docs page, lean PyPI install, community infra), the PR-by-PR history below.
Releases can now be triggered manually
Pushing the
v0.1.0tag from this session was refused — its git access is limited to the working branch, sorefs/tags/*is blocked. Rather than leaving the release blocked on a terminal only the owner has,release.ymlgains aworkflow_dispatchtrigger with atag_nameinput:softprops/action-gh-releasecreates the tag itself when giventag_name, so one manual run produces the tag, the GitHub release with the wheel attached, and (withPYPI_PUBLISH=true+ thepypienvironment) the PyPI publish. Tag-push releases behave exactly as before viagithub.ref_name.After merging, the release fires either way:
tag_name: v0.1.0.Also posted alongside this PR: the eight seed issues (#23–#30), four labeled
good first issue.🤖 Generated with Claude Code
https://claude.ai/code/session_01QVbxD1gd3gsC6zXKE6L3ya
Generated by Claude Code