Skip to content

Release/v0.2.1#16

Open
digitallysavvy wants to merge 19 commits into
mainfrom
release/v0.2.1
Open

Release/v0.2.1#16
digitallysavvy wants to merge 19 commits into
mainfrom
release/v0.2.1

Conversation

@digitallysavvy
Copy link
Copy Markdown
Contributor

Summary

  • Fix agora init and agora quickstart create failing on git clone in non-interactive environments by passing -c credential.helper= to the git subprocess, so public HTTPS quickstarts clone without consulting macOS keychain or other credential helpers.
  • Bump GitHub Actions to current major versions across CI, release, pages, govulncheck, and apt-repo workflows (actions/checkout@v6, actions/deploy-pages@v5, actions/setup-node@v6, Docker setup/login actions @v4).
  • Prepare the v0.2.1 release in CHANGELOG.md and update the build-time version comment in internal/cli/version.go.

Test plan

  • make test
  • go test ./internal/cli -run 'TestGitQuickstartCloneArgs|TestCloneQuickstartRepoLocal'

Disable git credential helpers for quickstart clone subprocesses so init and quickstart create work in non-interactive agent and CI environments.
Update checkout, deploy-pages, Docker setup, and setup-node actions to their latest major releases across CI, release, pages, and govulncheck workflows.
Prepare the 0.2.1 patch release in the changelog and version metadata.
@digitallysavvy digitallysavvy requested a review from plutoless May 19, 2026 21:10
@digitallysavvy digitallysavvy self-assigned this May 19, 2026
@digitallysavvy digitallysavvy added bug Something isn't working enhancement New feature or request labels May 19, 2026
…lity

Validate --ref and AGORA_QUICKSTART_<TEMPLATE>_REPO_URL overrides up front,
pre-flight git on PATH, and emit a clone:override progress event so workshop
and CI runs can see which fork was cloned. Adds error codes
QUICKSTART_REF_INVALID, QUICKSTART_REPO_OVERRIDE_INVALID, and
QUICKSTART_GIT_MISSING.
Require --template for non-interactive init runs, add projectSelectionReason
to init JSON output, default agora open to URL-only in CI/non-TTY sessions
with explicit --browser/--no-browser control, and block installer self-update
in CI unless AGORA_ALLOW_UPGRADE_IN_CI is set.
Document MCP progress caveats, headless CI init patterns, projectSelectionReason
and upgrade ciBlocked fields in automation.md, expand llms.txt for agents, and
update skills/MCP help with deterministic --new-project init examples.
Point go.mod and build ldflags at github.com/AgoraIO/cli, publish agora-cli_*
archives as the primary release artifact, keep agora-cli-go_* as a legacy alias,
and teach agora upgrade and the install scripts to prefer the new name with
fallback for older installs.
Fix CONTRIBUTING clone instructions to cd cli/, update npm package
repository.directory metadata, point the issue template docs link at docs/,
and mark the devex backlog contributor-path item shipped.
Select agora-cli-go_* archives only for v0.1.7–v0.2.0 targets and agora-cli_*
for v0.2.1+, drop the redundant legacy alias from GoReleaser, and document
upgrade paths, install examples, and the v0.2.1 release summary.
Consolidate all v0.2.1 changes under a single release section with updated
date, automation/upgrade/archive entries, and a link to docs/releases/v0.2.1.md.
Emit JSON-RPC notifications/progress when tools/call includes
_meta.progressToken. Wire progress through init, quickstart create,
and project create without writing NDJSON to the stdio transport.
Expose per-command automation hints so agents can tell which commands
require a browser or explicit arguments without inferring from help text.
Print a stderr tip pointing callers at --json or --format envelope when
the default dotenv output is used interactively without an explicit format.
Assert headlessSafe/interactivity in introspect output and exercise
representative commands documented in automation.md to catch doc drift.
Document MCP progress tokens, login NDJSON parsing, envelope versioning,
project env behavior, and config boolean flag syntax.
Add npm, manual tarball, and checksum verification options for
environments that block pipe-to-shell installers.
Fold upgrade notes into CHANGELOG.md and point RELEASING.md at the
changelog as the single release-notes source.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant