Skip to content

release: 0.6.3 — an administrator can give a colleague a new password - #221

Merged
ashwin-agami merged 2 commits into
mainfrom
release-0.6.3
Aug 11, 2026
Merged

release: 0.6.3 — an administrator can give a colleague a new password#221
ashwin-agami merged 2 commits into
mainfrom
release-0.6.3

Conversation

@ashwin-agami

Copy link
Copy Markdown
Contributor

Summary

Cuts 0.6.3. Two things ship in it:

Changes

No link reference added at the bottom of the changelog: that list stopped at 0.3.9 and 0.6.0–0.6.2 have none, so this matches recent practice rather than reviving a lapsed one.

Why this release is needed now

The private product's seat-and-password work calls mint_reset_token, which exists only from this version. That branch cannot open as a PR until this is on PyPI and its floor is raised.

Checklist

  • Spec: line present
  • All four version strings bumped and checked — no 0.6.2 left anywhere in the plugin or package metadata
  • Version-parity tests pass (test_marketplace_script_imports, test_sm_install_resolution) — they read the marketplace version directly
  • Changelog entry states what the reset does and what it does not: a live access token, the /admin cookie and an outstanding authorization code all survive it

The setup link works exactly once, so an administrator could create somebody's
account and never help them back into it, and with no mail path there is no
self-service reset either. `/claim` gains a second purpose: `setup` for a
pending account choosing its first password, `reset` for a claimed one being
given a new one. Matched against the state of the account rather than trusted
from the link, so neither can do the other's job.

Also carries #217's scoped `get_datasource_schema`, which landed after 0.6.2
and had been sitting in Unreleased.

Spec: ACE-108
Copilot AI lite review requested due to automatic review settings August 11, 2026 05:09

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Release housekeeping for 0.6.3, promoting changelog content and bumping version strings across the package and plugin metadata so the release can be published/installed consistently.

Changes:

  • Bump version from 0.6.2 → 0.6.3 in package + plugin/marketplace metadata.
  • Promote [Unreleased] to [0.6.3] and add detailed release notes for #220 and #217.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
plugins/agami/.claude-plugin/plugin.json Bumps plugin version to 0.6.3.
packages/agami-core/pyproject.toml Bumps Python package version to 0.6.3.
CHANGELOG.md Adds the 0.6.3 release section and moves previously-unreleased notes into it.
.claude-plugin/marketplace.json Bumps marketplace metadata + plugin entry versions to 0.6.3.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CHANGELOG.md Outdated
Comment on lines 46 to 47
### Changed

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed — good catch. My new section ended with a ### Changed and #217's existing one followed straight after, so the release's changes were split across two identical headings.

Folded into one: the 0.6.3 section is now ### Added / ### Changed / ### Fixed, with the claim-page wording, the event-loop offload and the get_datasource_schema scoping all under the single Changed list.

Review found two consecutive `### Changed` headings: the reset's entries
ended with one and #217's own followed immediately, so the release's changes
were split into two lists a reader would have to notice were the same thing.

Spec: ACE-108
@ashwin-agami
ashwin-agami merged commit f71f3c2 into main Aug 11, 2026
8 checks passed
@ashwin-agami
ashwin-agami deleted the release-0.6.3 branch August 11, 2026 05:25
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants