chore: rename tap and releases (#34)

* rename tap and releases

* skill version

* bootstrap 0.1.0

Author: cjkenned

.github/workflows/release.yml

@@ -52,7 +52,7 @@ jobs:
           # uploads archives, the source bundle, and the checksums file here.
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           # Cross-repo token (App-minted): lets goreleaser commit
-          # Formula/airbyte.rb to airbytehq/homebrew-tap.
+          # Formula/airbyte-cli.rb to airbytehq/homebrew-tap.
           HOMEBREW_TAP_GITHUB_TOKEN: ${{ steps.get-app-token.outputs.token }}
           # Skill version stamped into the binary via cmd.ExpectedSkillVersion.
           # Sourced from skills/airbyte-agents/SKILL.md by the previous step.

.github/workflows/skill-version-bump.yml

@@ -20,6 +20,13 @@ jobs:
         run: |
           set -euo pipefail
           head=$(./scripts/skill-version.sh)
+          # v0.1.0 is the documented bootstrap/reset version. Accept it
+          # regardless of the base branch so deliberate resets (e.g. after a
+          # namespace rename) don't require bypassing the check.
+          if [ "$head" = "v0.1.0" ]; then
+            echo "::notice::Head is v0.1.0 — treating as bootstrap/reset."
+            exit 0
+          fi
           if ! base=$(git show "origin/${{ github.base_ref }}":skills/airbyte-agents/SKILL.md 2>/dev/null | ./scripts/skill-version.sh /dev/stdin 2>/dev/null); then
             echo "::notice::Base branch has no skill version yet — accepting head=$head as the bootstrap."
             exit 0

.goreleaser.yaml

@@ -64,17 +64,20 @@ release:
   prerelease: auto
   name_template: "v{{ .Version }}"
 
-# Homebrew formula generation. Goreleaser commits Formula/airbyte.rb to the
-# airbytehq/homebrew-tap repo on each non-prerelease release. Cross-repo write
-# requires a separate token (HOMEBREW_TAP_GITHUB_TOKEN) — the default
+# Homebrew formula generation. Goreleaser commits Formula/airbyte-cli.rb to
+# the airbytehq/homebrew-tap repo on each non-prerelease release. Cross-repo
+# write requires a separate token (HOMEBREW_TAP_GITHUB_TOKEN) — the default
 # GITHUB_TOKEN issued by the workflow only has access to this repo.
 #
 # Note: `brews` is deprecated in goreleaser in favor of `homebrew_casks`. We are
 # intentionally still using `brews` because casks are intended for signed/notarized
 # macOS binaries and our binaries are unsigned. Revisit when goreleaser removes
 # `brews` entirely or when we start signing release binaries.
+#
+# Formula is named `airbyte-cli` (to match the repo); the installed binary
+# is `airbyte` (short, what users actually type).
 brews:
-  - name: airbyte
+  - name: airbyte-cli
     repository:
       owner: airbytehq
       name: homebrew-tap

README.md

@@ -28,7 +28,7 @@ Environment overrides:
 ### Homebrew (macOS, Linux)
 
 ```bash
-brew install airbytehq/tap/airbyte
+brew install airbytehq/tap/airbyte-cli
 ```
 
 ### Manual binary download
@@ -277,7 +277,7 @@ To add a new resource: implement the `Resource` interface in `internal/resources
 
 ## Releases
 
-Releases are cut by pushing a `v*` tag. The `release` workflow builds binaries for `linux`/`darwin`/`windows` × `amd64`/`arm64` (Windows arm64 excepted) via [goreleaser](https://goreleaser.com), uploads them as a draft GitHub release, and commits an updated `Formula/airbyte.rb` to [airbytehq/homebrew-tap](https://github.com/airbytehq/homebrew-tap).
+Releases are cut by pushing a `v*` tag. The `release` workflow builds binaries for `linux`/`darwin`/`windows` × `amd64`/`arm64` (Windows arm64 excepted) via [goreleaser](https://goreleaser.com), uploads them as a draft GitHub release, and commits an updated `Formula/airbyte-cli.rb` to [airbytehq/homebrew-tap](https://github.com/airbytehq/homebrew-tap).
 
 ### Versioning
 
@@ -303,13 +303,13 @@ Pre-releases use a suffix (`v0.2.0-rc1`, `v0.2.0-beta`); goreleaser publishes th
 
 3. **Watch the release workflow.** It runs in two halves:
    - Builds + uploads a **draft** GitHub release (binaries, archives, `checksums.txt`).
-   - Commits `Formula/airbyte.rb` to `airbytehq/homebrew-tap@main`.
+   - Commits `Formula/airbyte-cli.rb` to `airbytehq/homebrew-tap@main`.
 4. **Review the draft release.** Open it in the GitHub UI, check the auto-generated changelog, and either edit the notes or accept them.
 5. **Click Publish.** This is intentional manual gating — easy to catch a misconfigured formula or stale changelog before users see it.
 6. **Smoke-test the install** on a fresh machine:
 
    ```bash
-   brew install airbytehq/tap/airbyte
+   brew install airbytehq/tap/airbyte-cli
    airbyte agents version
    ```
 
@@ -320,7 +320,7 @@ Validate the release pipeline locally without pushing anything:
 ```bash
 goreleaser check                    # validates .goreleaser.yaml
 goreleaser release --snapshot --clean
-# inspect dist/ — binaries, archives, and dist/homebrew/Formula/airbyte.rb
+# inspect dist/ — binaries, archives, and dist/homebrew/Formula/airbyte-cli.rb
 ```
 
 The snapshot run produces real artifacts in `dist/` so you can confirm the formula renders correctly and the version-stamped ldflags resolve as expected. Nothing is uploaded.
@@ -329,7 +329,7 @@ The snapshot run produces real artifacts in `dist/` so you can confirm the formu
 
 - **Bad binaries, formula not yet committed.** Delete the draft release in the GitHub UI, delete the tag locally and remotely (`git tag -d v0.1.0 && git push origin :refs/tags/v0.1.0`), fix, retag.
 - **Formula already committed but binaries broken.** Delete the formula commit on `homebrew-tap` (open a one-line revert PR), then retag a new patch version. Don't re-use the same tag.
-- **Need to yank a published release.** Delete the formula commit on `homebrew-tap`. Existing `brew install`s won't rollback automatically; users with the broken version will keep it until they `brew upgrade airbyte`. Consider a `0.x.y+1` patch release rather than a yank when possible — fewer surprises for users.
+- **Need to yank a published release.** Delete the formula commit on `homebrew-tap`. Existing `brew install`s won't rollback automatically; users with the broken version will keep it until they `brew upgrade airbyte-cli`. Consider a `0.x.y+1` patch release rather than a yank when possible — fewer surprises for users.
 
 ## License
 

RELEASES.md

@@ -39,7 +39,7 @@ The script does **not** publish anything itself — pushing the tag is what trig
 2. Runs `goreleaser release --clean`, which:
    - Builds cross-platform binaries (linux/darwin/windows × amd64/arm64).
    - Creates a **draft** GitHub release in `airbyte-cli` with the archives and `checksums.txt` attached.
-   - Commits an updated `Formula/airbyte.rb` directly to `main` on `airbytehq/homebrew-tap`.
+   - Commits an updated `Formula/airbyte-cli.rb` directly to `main` on `airbytehq/homebrew-tap`.
 
 Prerelease tags (e.g. `v0.1.0-rc1`) are detected automatically: the GitHub release is still created (as a prerelease draft) but the brew formula commit is **skipped** (`skip_upload: auto` in `.goreleaser.yaml`).
 
@@ -57,7 +57,7 @@ Two ways to publish:
 gh release edit vX.Y.Z --draft=false --repo airbytehq/airbyte-cli
 ```
 
-Once published, the tarball URLs in the brew formula resolve and `brew install airbytehq/tap/airbyte` works. Before publishing, those URLs return 404 to anonymous requests (which is what `brew` makes).
+Once published, the tarball URLs in the brew formula resolve and `brew install airbytehq/tap/airbyte-cli` works. Before publishing, those URLs return 404 to anonymous requests (which is what `brew` makes).
 
 ## Removing a tag
 
@@ -76,7 +76,7 @@ git tag -d vX.Y.Z
 git push origin :refs/tags/vX.Y.Z
 ```
 
-**3. Revert the formula commit on `homebrew-tap`** if goreleaser already pushed one. Find the bump commit in `https://github.com/airbytehq/homebrew-tap/commits/main` and revert it (or push a follow-up commit restoring the previous formula). If this is the first release, just delete `Formula/airbyte.rb` from the tap.
+**3. Revert the formula commit on `homebrew-tap`** if goreleaser already pushed one. Find the bump commit in `https://github.com/airbytehq/homebrew-tap/commits/main` and revert it (or push a follow-up commit restoring the previous formula). If this is the first release, just delete `Formula/airbyte-cli.rb` from the tap.
 
 **4. Re-run the release script** when ready:
 

internal/versioncheck/check.go

@@ -113,7 +113,7 @@ func maybeNudge(currentRaw string, current semver, c *cacheFile, stderr io.Write
 func formatNudge(current, latest, releaseURL string) string {
 	var b strings.Builder
 	fmt.Fprintf(&b, "A new version of the airbyte CLI is available: %s (you have %s)\n", latest, current)
-	b.WriteString("  Upgrade with brew: brew upgrade airbyte\n")
+	b.WriteString("  Upgrade with brew: brew upgrade airbyte-cli\n")
 	b.WriteString("  Or reinstall:      curl -fsSL https://airbyte.ai/install.sh | sh\n")
 	if releaseURL != "" {
 		fmt.Fprintf(&b, "  Release notes:     %s\n", releaseURL)

scripts/release.sh

@@ -70,7 +70,7 @@ echo
 echo "Tag pushed. The release workflow will:"
 echo "  - build cross-platform archives"
 echo "  - create a DRAFT release at https://github.com/airbytehq/airbyte-cli/releases"
-echo "  - commit Formula/airbyte.rb to airbytehq/homebrew-tap"
+echo "  - commit Formula/airbyte-cli.rb to airbytehq/homebrew-tap"
 echo
 echo "Watch the run:    gh run watch --repo airbytehq/airbyte-cli"
 echo "Publish the draft once you've eyeballed the artifacts and the formula commit."

skills/airbyte-agents/SKILL.md

@@ -2,13 +2,13 @@
 name: airbyte-agents
 description: Drive the `airbyte agents` CLI namespace to manage Airbyte connectors, workspaces, and organizations. Run list/get/search/create/update actions against connector data (HubSpot, Salesforce, Slack, GitHub, etc.), install new connectors via the browser credential flow, list and switch workspaces, list organizations, inspect a connector's entities and actions, or print the merged CLI + OpenAPI schema for any operation. Use when the user mentions Airbyte, the `airbyte` CLI, connectors, syncs, workspaces, organizations, or asks to read/write data from a connected SaaS product.
 metadata:
-  version: "v0.1.3"
+  version: "v0.1.0"
 ---
 
 # airbyte agents
 
 > [!NOTE]
-> Requires the `airbyte` CLI on `PATH`. Install via `brew install airbytehq/tap/airbyte` or `curl -fsSL https://airbyte.ai/install.sh | bash`. See the [project README](https://github.com/airbytehq/airbyte-cli#install) for other options.
+> Requires the `airbyte` CLI on `PATH`. Install via `brew install airbytehq/tap/airbyte-cli` or `curl -fsSL https://airbyte.ai/install.sh | bash`. See the [project README](https://github.com/airbytehq/airbyte-cli#install) for other options.
 
 The CLI is invoked as `airbyte agents <resource> <operation>`. It exposes Airbyte's data plane through a uniform interface — every command takes a JSON payload and returns JSON.