Skip to content

Conversation

@hiroTamada
Copy link
Contributor

@hiroTamada hiroTamada commented Jan 12, 2026

Summary

  • Update all references from the old organization name (onkernel) to the new organization name (kernel)
  • This fixes the goreleaser release workflow which was failing due to the old org name

Changes

  • Update go.mod module path to github.com/kernel/hypeman
  • Update all Go import statements (120 files)
  • Update .goreleaser.yaml release owner
  • Update documentation (README, RELEASES.md, lib READMEs)
  • Update install/uninstall scripts with new GitHub URLs
  • Update kernel download URLs in lib/system/versions.go
  • Update stainless.yaml SDK configuration

Test plan

  • go build ./... passes
  • Release workflow should now work correctly

Note

Aligns repository with new GitHub org and fixes release paths.

  • Update go.mod to github.com/kernel/hypeman; rewrite all Go imports to github.com/kernel/...
  • Change GoReleaser owner to kernel; fix badges and links in README.md/RELEASES.md
  • Update install/uninstall and UTM scripts to new GitHub URLs and Homebrew tap
  • Revise kernel download URLs and docs to kernel/linux in lib/system/* (versions, README)
  • Adjust SDK config in stainless.yaml to kernel repos and package paths
  • No functional logic changes aside from path updates; builds/tests reference new module paths

Written by Cursor Bugbot for commit cc88f12. This will update automatically on new commits. Configure here.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

✱ Stainless preview builds

This PR will update the hypeman SDKs with the following commit message.

chore: rename org from onkernel to kernel
⚠️ hypeman-typescript studio · code

There was a regression in your SDK.
generate ⚠️build ✅lint ✅test ✅

npm install https://pkg.stainless.com/s/hypeman-typescript/00e5bed7e445fcedb3afce33893c06892a6059fb/dist.tar.gz
⚠️ hypeman-go studio · code

There was a regression in your SDK.
generate ⚠️lint ✅test ✅

go get github.com/stainless-sdks/hypeman-go@5dc073af55b32be1e18546a2d98fcdc240ebae90
⚠️ hypeman-cli studio · conflict

There was a regression in your SDK.


This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
Last updated: 2026-01-12 19:14:33 UTC

@hiroTamada hiroTamada force-pushed the rename-org-to-kernel branch from 923b68b to 5d08324 Compare January 12, 2026 16:29
@hiroTamada hiroTamada requested a review from rgarcia January 12, 2026 16:29
@tembo
Copy link

tembo bot commented Jan 12, 2026

Nice cleanup overall — looks like a straight org rename across code + tooling.

A couple things worth double-checking:

  • README.md: the Homebrew command still points at onkernel/tap/hypeman while the rest of the doc is switched to kernel/.... If the tap moved with the org rename, it should probably be updated here too; if it didn’t move, I’d consider adding a short note so users don’t assume everything is under kernel now.

    brew install kernel/tap/hypeman
    
  • stainless.yaml: similarly, publish.homebrew.tap_repo is still onkernel/homebrew-tap while other production_repo values are now kernel/.... If the tap repo is intentionally staying under onkernel, maybe call that out in the PR description (or keep README consistent with that). If it moved, this should likely follow.

  • lib/system/versions.go: swapping the kernel download URLs to github.com/kernel/linux makes sense. Given how many URLs are hardcoded, it might be worth extracting a const linuxReleasesBase = "https://github.com/kernel/linux/releases/download" (or similar) to reduce the chance of future mismatches if the org/repo changes again.

Reasoning: most of this PR is mechanical renames, so the main risk is leaving a few user-facing URLs/configs half-migrated (Homebrew/tap + docs) and causing confusing install instructions.

@hiroTamada hiroTamada requested a review from tnsardesai January 12, 2026 16:30
Update all references from the old organization name (onkernel) to
the new organization name (kernel):

- Update go.mod module path to github.com/kernel/hypeman
- Update all Go import statements
- Update .goreleaser.yaml release owner
- Update documentation and scripts with new GitHub URLs
- Update kernel download URLs in lib/system/versions.go
@hiroTamada hiroTamada force-pushed the rename-org-to-kernel branch from 5d08324 to 1acdb40 Compare January 12, 2026 16:57
homebrew:
tap_repo: onkernel/homebrew-tap
homepage: https://github.com/onkernel/hypeman
homepage: https://github.com/kernel/hypeman
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incomplete organization rename in stainless SDK config

High Severity

The homepage URL was changed to kernel but multiple other repo references in stainless.yaml still use onkernel: production_repo fields for Go, CLI, and TypeScript SDKs (lines 24, 30, 41), go_sdk_package (line 32), and tap_repo (line 35). The bootstrap script shows all repos were renamed to kernel/, so these are missed updates. This inconsistency will cause SDK generation and Homebrew publishing to fail since they'll reference non-existent onkernel repos.

Fix in Cursor Fix in Web

Copy link
Contributor

@rgarcia rgarcia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, just one missed reference

stainless.yaml Outdated
go_sdk_package: github.com/onkernel/hypeman-go
publish:
homebrew:
tap_repo: onkernel/homebrew-tap
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be kernel/homebrew-tap

@hiroTamada
Copy link
Contributor Author

Fixed! Updated tap_repo to kernel/homebrew-tap and also updated the brew install commands in README.md and scripts/utm/README.md to use kernel/tap/hypeman.

@hiroTamada hiroTamada merged commit e77731d into main Jan 12, 2026
4 checks passed
@hiroTamada hiroTamada deleted the rename-org-to-kernel branch January 12, 2026 19:12
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.

3 participants