Skip to content

fix(skill): Hono quick starts omit adapter deprecation and the preferred framework integration #187

Description

@coygeek

Summary

The supabase-server skill still presents the Hono adapter as its normal quick-start route without the adapter deprecation notice. The README shipped in the same @supabase/server@1.9.0 package says adapters are deprecated, scheduled for removal on December 1, 2026, and directs framework integration to middleware bridges. An agent following the skill alone receives different lifecycle guidance from the package README.

Steps to reproduce

  1. Inspect the npm tarball for @supabase/server@1.9.0, or the files at main revision 99eb65cebe55abb03881bd70a2e089b3a1db745f.
  2. Read skills/supabase-server/SKILL.md, especially its entry-point table and Quick starts / Hono section.
  3. Compare the imports and surrounding guidance with README.md / Framework Adapters.
  4. Observe that the skill recommends @supabase/server/adapters/hono in its Hono examples without marking it deprecated or giving its removal date, while the README recommends middleware bridges and the framework integration guide.

Expected behavior

The skill should communicate the same adapter lifecycle and preferred integration route as the README before an agent chooses a framework integration. New Hono guidance should lead to the maintained framework integration documented by the package. Any retained adapter examples should make their deprecated status and migration route clear.

Actual behavior

The skill's entry-point table lists the Hono adapter, and its two Hono quick starts import that adapter. Neither section includes the deprecation or removal date. A later documentation-table link to the adapter-free framework guide does not qualify those quick starts.

Affected area

skills/supabase-server/SKILL.md, particularly the entry-point table and Hono quick starts.

Runtime or environment

Verified by source comparison at main@99eb65cebe55abb03881bd70a2e089b3a1db745f and by inspecting the published @supabase/server@1.9.0 tarball. The packaged skill is byte-identical to the skill at that revision. This is a documentation consistency report; no generated application or adapter runtime was executed.

Evidence

Impact

Agents loading the recommended skill can start new integrations on an API already scheduled for removal and miss the current migration guidance.

Additional context

The closure check is to compare the skill's framework selection and Hono quick starts with the current README lifecycle contract. It passes when the skill makes the deprecation and preferred integration route explicit before selecting an adapter. This report does not request an adapter runtime change.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions