Skip to content

chore: Remove Gemfury and CircleCI from the codebase#2933

Open
barnabasbusa wants to merge 2 commits intomainfrom
bbusa/remove-gemfury
Open

chore: Remove Gemfury and CircleCI from the codebase#2933
barnabasbusa wants to merge 2 commits intomainfrom
bbusa/remove-gemfury

Conversation

@barnabasbusa
Copy link
Collaborator

Summary

  • Remove GoReleaser Gemfury publisher (packages now published via GitHub Pages)
  • Remove FURY_TOKEN / GEMFURY_PUBLISH_TOKEN from build scripts and workflows
  • Remove gemfury-publisher CircleCI context
  • Update remaining apt source URLs in CI to sdk.kurtosis.com
  • Delete .circleci/config.yml entirely (all CI is on GitHub Actions now)

Follow-up

Test plan

  • Verify publish workflow still succeeds without Fury token
  • Verify update-package-repo workflow still publishes deb/rpm to GitHub Pages

🤖 Generated with Claude Code

barnabasbusa and others added 2 commits March 5, 2026 14:25
Packages are now published to GitHub Pages via the
update-package-repo workflow, making the Gemfury publisher
completely redundant.

- Remove GoReleaser fury.io publisher block
- Remove FURY_TOKEN export from build.sh
- Remove GEMFURY_PUBLISH_TOKEN from publish workflow
- Remove gemfury-publisher context from CircleCI
- Update CircleCI + GitHub Actions apt sources to new URL
- Remove "like Gemfury" comment from update-package-repo workflow

The GEMFURY_PUBLISH_TOKEN secret can now be removed from GitHub.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
All CI/CD has been migrated to GitHub Actions. The CircleCI config
is no longer used and can be safely removed.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@barnabasbusa barnabasbusa changed the title Remove Gemfury and CircleCI from the codebase chore :Remove Gemfury and CircleCI from the codebase Mar 5, 2026
@barnabasbusa barnabasbusa changed the title chore :Remove Gemfury and CircleCI from the codebase chore: Remove Gemfury and CircleCI from the codebase Mar 5, 2026
@barnabasbusa barnabasbusa requested a review from tedim52 March 5, 2026 13:26
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