Skip to content

chore: fix local pod build issue + remove CircleCI config#14504

Merged
dylanjeffers merged 1 commit into
mainfrom
chore/remove-circleci-config
Jun 23, 2026
Merged

chore: fix local pod build issue + remove CircleCI config#14504
dylanjeffers merged 1 commit into
mainfrom
chore/remove-circleci-config

Conversation

@dylanjeffers

Copy link
Copy Markdown
Contributor

Summary

Two related housekeeping items. One of them (the pod fix) turned out to have no repo delta — see below.

1. Local pod build issue — fixed locally, no repo change

pod install was aborting with a fmt version conflict:

[!] CocoaPods could not find compatible versions for pod "fmt":
  ... fmt (= 12.1.0) ... fmt (= 11.0.2)

Root cause: the local node_modules/react-native podspecs had been hand-edited (mtime May 22) to bump fmt 11.0.2 → 12.1.0 across ~16 podspecs (third-party-podspecs/fmt.podspec, RCT-Folly.podspec, and the ReactCommon/React-* set). This was an abandoned experiment that predates the committed fix in #14403 (May 27), where we deliberately kept fmt at 11.0.2 and patched base.h via the Podfile post_install instead ("no equivalent backport exists for 0.79-stable yet"). The committed Podfile.lock pins 11.0.2, so the stale local 12.1.0 podspecs conflicted with it.

Fix: restored the drifted node_modules podspecs to the pristine react-native@0.79.5 versions (which are 11.0.2 — matching the committed lockfile) and cleared CocoaPods' stale Pods/Local Podspecs/ cache. pod install now completes, and the committed base.h patch applies cleanly ("Patched Pods/fmt/include/fmt/base.h … fmt 11.0.2 compat").

Because the drift was entirely in gitignored node_modules/Pods, there is no repository change for this — the committed state was already correct and reproducible (a fresh npm install ships fmt 11.0.2). Documented here for the record; the only thing in this PR is the CircleCI removal below.

2. Remove CircleCI config

CircleCI is fully disabled — the setup gate is equal: ['disabled', 'enabled'] (always false) — and is not coming back. Removed the entire .circleci/ tree (55 files, ~3,100 lines) plus dangling references:

  • Dropped the validate-ci-config npm script.
  • Removed .circleci/continue_config.yml from .gitignore.
  • Removed the stale CircleCI build badge from packages/web/README.md.
  • Preserved the one live dependency: the GitHub Actions publish-packages.yml workflow generates its Slack message from publish-packages-template.jq, which lived under .circleci/slack-templates/. Moved it to scripts/slack-templates/ and repointed scripts/publish-packages-slack-template.sh.

Follow-up (not in this PR)

The web/mobile GitHub Actions workflows still list - '.circleci/**' as a path-trigger. These are now no-op globs (the dir is gone). I left them out because editing .github/workflows/*.yml requires the workflow OAuth scope, which this client lacks. Trivial one-line cleanup for a follow-up with the right scope.

🤖 Generated with Claude Code

CircleCI is fully disabled — the setup gate is `equal: ['disabled',
'enabled']`, which is always false — and is not coming back. Remove the
entire `.circleci/` tree (config.yml, continue_config.yml, src/, scripts,
slack-templates, hooks) and clean up dangling references:

- Drop the `validate-ci-config` npm script (packed/validated the CircleCI
  config).
- Remove `.circleci/continue_config.yml` from .gitignore.
- Remove the stale CircleCI build badge from packages/web/README.md.

Preserve the one live dependency: `publish-packages.yml` (GitHub Actions)
generates its Slack message from `publish-packages-template.jq`, which
lived under `.circleci/slack-templates/`. Move it to
`scripts/slack-templates/` and update `scripts/publish-packages-slack-template.sh`
to point there.

Note: the dead `.circleci/**` path-filter entries in the web and mobile
GitHub Actions workflows are left as-is here (editing workflow files
requires the `workflow` OAuth scope); they are now no-op globs and can be
cleaned up in a follow-up.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Jun 23, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 15c81e5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security

Copy link
Copy Markdown

Dependency limit exceeded — report not shown.

This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report.

Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard.

Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account.

@github-actions

Copy link
Copy Markdown
Contributor

🌐 Web preview ready

Preview URL: https://audius-web-preview-pr-14504.audius.workers.dev

Unique preview for this PR (deployed from this branch).
Workflow run

@dylanjeffers dylanjeffers merged commit 771508b into main Jun 23, 2026
13 checks passed
@dylanjeffers dylanjeffers deleted the chore/remove-circleci-config branch June 23, 2026 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant