Skip to content

chore(main): release 1.14.0 - #92

Merged
lxcong merged 1 commit into
mainfrom
release-please--branches--main--components--agentkey-skill
Aug 22, 2026
Merged

chore(main): release 1.14.0#92
lxcong merged 1 commit into
mainfrom
release-please--branches--main--components--agentkey-skill

Conversation

@lxcong

@lxcong lxcong commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.14.0 (2026-08-22)

Features

  • add Cursor, Gemini CLI, and Antigravity plugin support (#91) (49a015b)
  • add DeepSeek Harness and Kimi MCP routing (#96) (97e3ab2)

Bug Fixes

  • claude: restore native MCP OAuth login (#95) (efc2809)
  • plugins: package Gemini releases and improve OAuth (#94) (fbec683)

This PR was generated with Release Please. See documentation.

lxcong pushed a commit that referenced this pull request Aug 11, 2026
## Summary

- preserve the existing `agentkey.skill` GitHub Release asset and add
platform-named Gemini extension archives for macOS, Linux, and Windows
- opt the Gemini extension into native first-connect OAuth with
`oauth.enabled`, while keeping `/mcp auth agentkey` as the manual retry
path
- add explicit Gemini, Antigravity 2.0, and Antigravity CLI
authentication and connection-verification guidance
- explain Gemini's user-Skill precedence warning and avoid duplicate MCP
registrations when an extension or plugin already owns the server entry
- add regression coverage and trigger the scripts test workflow when
authentication guidance or release packaging changes

## Root causes

Gemini CLI treats a lone generic GitHub Release asset as the extension
archive. AgentKey releases currently publish only `agentkey.skill`, but
Gemini CLI extracts only `.tar.gz` and `.zip` extension archives. After
that extraction failure, Gemini retries Git clone in the same non-empty
temporary directory and fails again.

Separately, the Gemini manifest omitted `oauth.enabled`. Gemini
discovered that AgentKey required OAuth, but only reported `/mcp auth
agentkey` instead of starting the browser flow automatically. A
pre-existing user Skill at `~/.agents/skills/agentkey` can also override
the extension-bundled Skill, hiding new setup guidance even though the
extension MCP entry is active.

## Authentication design

- Gemini uses `httpUrl` plus `oauth.enabled: true`; OAuth endpoints and
client registration remain dynamically discovered.
- Antigravity keeps the documented credential-free `serverUrl`
configuration and uses DCR through its native Authenticate controls.
- No static access token, Authorization header, OAuth client secret, or
hard-coded authorization endpoint is added to either package.

## Validation

- Bats suite: 27/27 passing
- `gemini extensions validate .`
- built and inspected `agentkey.skill`, `darwin.agentkey.tar.gz`,
`linux.agentkey.tar.gz`, and `win32.agentkey.zip`
- verified both Gemini platform archive formats contain `oauth.enabled:
true`, `gemini-extension.json`, and `skills/agentkey/SKILL.md`
- validated workflow YAML, shell syntax, archive roots, manifest
invariants, and `git diff --check`
- verified the live AgentKey endpoint advertises protected-resource
metadata, PKCE, and a dynamic client registration endpoint

## Release coordination

Merge this fix before release PR #92 so the first Gemini-enabled release
publishes compatible archives and the corrected first-connect OAuth
behavior.

---------

Co-authored-by: Allen <0xfatdog@gmail.com>
@lxcong
lxcong force-pushed the release-please--branches--main--components--agentkey-skill branch 2 times, most recently from 8ba4d65 to 11e1a46 Compare August 13, 2026 18:24
@lxcong
lxcong force-pushed the release-please--branches--main--components--agentkey-skill branch from 11e1a46 to 0ac9f59 Compare August 22, 2026 20:05
@lxcong
lxcong merged commit def7706 into main Aug 22, 2026
9 checks passed
@lxcong
lxcong deleted the release-please--branches--main--components--agentkey-skill branch August 22, 2026 20:07
@lxcong

lxcong commented Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant