Skip to content

Release prep: 0.1.0 changelog and manually-triggerable releases - #31

Merged
Joshuaakaspace merged 2 commits into
mainfrom
claude/semantica-repo-evaluation-essnux
Sep 20, 2026
Merged

Joshuaakaspace merged 2 commits into
mainfrom
claude/semantica-repo-evaluation-essnux

Conversation

@Joshuaakaspace

Copy link
Copy Markdown
Collaborator

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.0 tag from this session was refused — its git access is limited to the working branch, so refs/tags/* is blocked. Rather than leaving the release blocked on a terminal only the owner has, release.yml gains a workflow_dispatch trigger with a tag_name input: softprops/action-gh-release creates the tag itself when given tag_name, so one manual run produces the tag, the GitHub release with the wheel attached, and (with PYPI_PUBLISH=true + the pypi environment) the PyPI publish. Tag-push releases behave exactly as before via github.ref_name.

After merging, the release fires either way:

  • I can trigger it via the Actions API on request, or
  • Actions tab → Release → Run workflow → 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

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
@Joshuaakaspace
Joshuaakaspace merged commit 4ce2d43 into main Sep 20, 2026
2 checks passed
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.

2 participants