Skip to content

chore!: rename graycode back to hawk - #301

Merged
Patel230 merged 4 commits into
mainfrom
chore/rename-back-to-hawk
Sep 11, 2026
Merged

chore!: rename graycode back to hawk#301
Patel230 merged 4 commits into
mainfrom
chore/rename-back-to-hawk

Conversation

@Patel230

@Patel230 Patel230 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Summary

The GitHub repository is GrayCodeAI/hawk again, so this reverses the rename in #272 and #280, with no legacy shims:

  • Module: github.com/GrayCodeAI/hawk
  • Binary: hawk
  • Env vars: HAWK_*
  • Config: ~/.hawk
  • Paths: cmd/hawk, internal/hawkerr, npm/hawk*, .github/actions/checkout-eyrie
  • Router dependency: github.com/GrayCodeAI/eyrie again (Eyrie* types, eyrieengine, EYRIE_*)
  • storage.ProviderConfigPath mirrors Eyrie's resolution: EYRIE_CONFIG_DIR, then <user config dir>/eyrie. There is no HAWK_CONFIG_DIR fallback.
  • The safety checks protect that path and no longer block the retired HAWK_CONFIG_DIR/provider.json.
  • The graycode rename plan and the rename narrative in CHANGELOG.md are removed.
  • EcosystemReport.Eyre is renamed to Eyrie.
  • Docs no longer describe the compatibility fallback.

These names are unchanged:

  • GrayCodeAI
  • graycodeai
  • graycode-skills
  • graycode-platform
  • graycode-cloud and the graycode-cloud.graph/v1 schema (graycode-platform uses them)
  • graycode-eco

The CLI's cloud wire names match graycode-platform again (HAWK_CLOUD, HawkCloudService, hawk capability).

Verification

Run locally through a go.work linking hawk and eyrie (GrayCodeAI/eyrie#118):

  • gofmt is clean.
  • go build ./..., go vet ./... and go test ./... all pass.
  • All six scripts/check-* boundary guards pass.

Blocked on

CI checks out eyrie main, which still declares module github.com/GrayCodeAI/graycode-router, so module hygiene, vet and tests fail until GrayCodeAI/eyrie#118 merges. go.mod also needs a new eyrie release: the v0.0.1 tag declares the old module path.

🤖 Generated with Claude Code

The GitHub repository is GrayCodeAI/hawk again, so the module, binary and
config surface follow it: github.com/GrayCodeAI/hawk, hawk binary, HAWK_*
env vars, ~/.hawk, cmd/hawk, internal/hawkerr, npm/hawk*. The router
dependency is github.com/GrayCodeAI/eyrie again (Eyrie* types,
eyrieengine, EYRIE_* env vars).

graycode-skills, graycode-platform, graycode-cloud and the
graycode-cloud.graph/v1 schema keep their names. Hard break with no
~/.graycode migration. Module-mode builds need a new eyrie release: the
eyrie v0.0.1 tag declares the graycode-router module path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Patel230 and others added 3 commits September 11, 2026 11:47
ProviderConfigPath mirrors Eyrie's resolution (EYRIE_CONFIG_DIR, then the
user config dir under eyrie) instead of falling back to HAWK_CONFIG_DIR,
and the safety checks no longer block the retired
HAWK_CONFIG_DIR/provider.json path. Removes the graycode rename plan and
the rename narrative in CHANGELOG, fixes the EcosystemReport.Eyre field
name, and updates docs that described the compatibility fallback.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
v0.3.0 is the first eyrie release whose go.mod declares
github.com/GrayCodeAI/eyrie after the rename back from graycode-router.
v0.0.1 declared the old path, which broke every CI job that resolves
modules without the local go.work.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
eyrie v0.3.0 was already recorded in the Go module proxy and checksum
database (May 2026, old module path github.com/hawk/eyrie), so every CI
job that resolved it failed with a checksum mismatch. v0.6.0 is the
rename-back release; its go.sum hashes match sum.golang.org.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Patel230
Patel230 merged commit 7d0d318 into main Sep 11, 2026
26 checks passed
@Patel230
Patel230 deleted the chore/rename-back-to-hawk branch September 11, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant