Repository navigation
chore(release): bump to 0.5.0 - #28
Conversation
Batched release of the three improvements merged since v0.4.1: - feat(server): HTTP transport config hardening + /healthz route (#16) - fix(profiles): persist hyperlink profile values and verify the write (#22) - feat(activities): create_activity to/cc/bcc recipient roles (#23) Minor bump: #16 and #23 add new surface (a /healthz route, argparse CLI, and to/cc/bcc activity parameters), #22 is a bug fix. No breaking change to the default stdio transport. Adds release-notes/v0.5.0.md. Pushing this version change to main triggers publish.yml to tag v0.5.0, create the GitHub Release, and publish to PyPI via OIDC.
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Summary
This is a clean release-preparation PR containing only two changes:
-
pyproject.toml— version bump from0.4.1→0.5.0. The change is correct and consistent with the semver rationale described in the PR body (new surface from #16 and #23, bug fix from #22, no breaking changes to the default stdio transport). -
release-notes/v0.5.0.md— new release notes file. The content accurately covers all three bundled changes, the behaviour-change callout for networked operators is appropriately prominent, and the intentional--htpptypo on line 22 correctly illustrates the old silent-fallback behaviour. The placeholder "Full Changelog" line is acknowledged and expected per convention.
No blocking defects found. This PR is ready to merge.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
Summary
Batched release of the three improvements merged since v0.4.1. Bumps
versionto 0.5.0 inpyproject.tomland addsrelease-notes/v0.5.0.md.Merging this PR to
maintriggers the release. Thepublish.ymlworkflow fires on aversionchange underpyproject.tomlonmain: it validates the package, creates thev0.5.0tag and GitHub Release, and publishes to PyPI via OIDC Trusted Publishing.What's being released
/healthzroute (HTTP transport config hardening: strict env parsing, argparse, path validation, health route #16) — strict env/flag parsing, argparse CLI with--help,ACCELO_MCP_PATHvalidation, a startup security log, and aGET /healthzliveness route. Networked-deployment misconfigurations now fail at startup instead of running in a surprising mode. Default stdio is unchanged.accelo_set_profile_valuenow uses the dedicated profile-value endpoint with typed bodies and a read-back verify, so it can no longer report a silent no-op asok.to/cc/bccparameters so an activity can be addressed to named recipients; owner remains the sender; the no-recipient path is unchanged.Why minor (0.5.0)
#16 and #23 add new surface (a route, CLI flags, new tool parameters); #22 is a bug fix folded in. No breaking change to the default stdio transport, so this is a minor bump rather than major.
Notes
release-notes/v0.5.0.md"Full Changelog" compare URL is left for the maintainer to finalise on release, matching the convention used for v0.4.1.main(PRs feat(server): harden HTTP transport config and add a health route #25, fix(profiles): persist hyperlink profile values and verify the write #26, feat(activities): let create_activity set to/cc/bcc recipient roles #27).