Skip to content

PLAN.md

Latest commit

 

History

History
162 lines (114 loc) · 6.91 KB

PLAN.md

File metadata and controls

162 lines (114 loc) · 6.91 KB
Raw

gws Release Plan

Planning snapshot for the post-v1.38.0 backlog. This file is a proposed sequence, not release authorization. Do not start implementation, merge, tag, publish, or close release-scoped issues from this file alone; wait for explicit user or CTO direction.

Release Requirements

Every release-scoped issue must include matching tests and skill/docs updates when applicable, even if the GitHub issue text does not explicitly mention them.

  • Tests should cover the changed command behavior, request construction, output shape, and important error paths.
  • Skills and command references should be updated for any new flag, command, output field, workflow, or behavioral caveat.
  • If no skill/docs change is needed, the PR should say why in its testing or implementation notes.

Current Baseline

  • Current released version: v1.38.0
  • Released on: 2026-04-30
  • Shipped issues:
    • #179: Drive resolve-comment / unresolve-comment now use Replies.Create with action=resolve|reopen
    • #181: Gmail read / thread surface attachments[] with attachment_id
    • #182: new gws chat recent --since <window> recap across active spaces

v1.39.0 - Homebrew Distribution

#115: Homebrew distribution

Scope:

  • Publish gws via a Homebrew tap.
  • Start with a formula that consumes the existing GitHub release binaries and checksums.
  • Add install/upgrade instructions to README and release notes.
  • Update release process documentation for tap updates.
  • Evaluate GoReleaser only if the current Makefile release flow becomes a bottleneck.

Acceptance:

  • brew tap omriariav/tap and brew install gws work on macOS.
  • Formula points at published release assets and verifies checksums.
  • Release process clearly states how the formula is updated.

v1.40.0 - OS Keychain Token Storage

#112: OS keychain token storage

Scope:

  • Add an optional keychain-backed token store for macOS and supported Linux environments.
  • Preserve compatibility with the existing JSON token file.
  • Provide migration or fallback behavior that does not strand existing users.

Acceptance:

  • Existing installs keep working without manual migration.
  • Keychain storage can be enabled and verified.
  • Failure modes fall back or report clear remediation.

v1.41.0 - Multi-Account Contexts

#113: Multi-account support with context switching

Scope:

  • Add named auth contexts for multiple Google accounts.
  • Support context selection by command, config, or environment variable.
  • Keep context-aware token/config storage compatible with the v1.40 token-store decision.

Acceptance:

  • Users can add, list, use, and remove contexts.
  • Commands run against the selected context.
  • Existing single-account config remains the default path.

v1.42.0 - Gmail Settings API

#104: Gmail settings API

Scope:

  • Add Gmail settings commands for vacation responder, filters, forwarding, IMAP/POP, and send-as where supported by the API and scopes.
  • Keep the first slice focused on read/list plus the most common writes if the full surface is too large.

Acceptance:

  • Commands follow existing gmail command patterns.
  • Required scopes are documented and covered by auth validation.
  • Tests cover request construction and output shape.

v1.43.0 - Service Account Support

#116: Service account support with domain-wide delegation

Scope:

  • Add service-account authentication for Workspace automation.
  • Support subject impersonation for domain-wide delegation.
  • Make credential loading and config explicit, with clear safety boundaries.

Acceptance:

  • Service-account login/status works separately from user OAuth.
  • Commands can run with the delegated subject where APIs support it.
  • Errors explain missing delegation, scopes, or admin setup.

v1.44.0 - Output Filtering

#117: jq / Go template output filtering

Scope:

  • Add structured output filtering flags such as --jq and/or --template.
  • Apply after API response normalization and before final printing.
  • Keep behavior consistent across services.

Acceptance:

  • Filters work with JSON output and fail clearly on invalid expressions.
  • Template output is deterministic and documented.
  • Tests cover success and invalid-filter paths.

v1.45.0 - Cross-Service Batch Operations

#123: Cross-service batch operations

Scope:

  • Add batch workflows for common multi-item operations across supported services.
  • Start with narrowly scoped operations that already have stable single-item commands.
  • Include dry-run and confirmation controls for destructive operations.

Acceptance:

  • Batch operations are scriptable and safe by default.
  • Destructive paths support dry-run or explicit confirmation.
  • Partial failures are reported in structured output.

v1.46.0 - Apps Script

#122: Google Apps Script - list, get, run

Scope:

  • Add initial Apps Script service support.
  • Include project listing, content inspection, and function invocation if scopes and API enablement allow it.

Acceptance:

  • New service follows existing command, client, scope, and test patterns.
  • API enablement or permission errors are understandable.

v1.47.0 - Classroom

#121: Google Classroom - courses, assignments, submissions

Scope:

  • Add initial Classroom service support for courses, assignments, and submissions.
  • Keep the first release read-focused unless write operations become clearly required.

Acceptance:

  • New service follows existing command, client, scope, and test patterns.
  • Outputs are useful for agents and scripts.

v1.48.0 - Extension System

#118: Extension / plugin system

Scope:

  • Design and implement a minimal extension mechanism for custom commands.
  • Treat this as a larger architecture release because it affects command discovery, trust, install paths, and execution boundaries.

Acceptance:

  • Extension install/list/remove flows are explicit.
  • Execution model is documented and constrained.
  • Core commands remain stable and unaffected.

Closed Or Deferred Items

  • #114: scoped auth is already addressed by gws auth login --services.
  • #164: quiet flag enforcement shipped in v1.35.0.
  • #172: docs replace-content already exists.