Disable GitHub Actions workflows (org-wide enablement migration)#536
Merged
Conversation
Move .github/workflows/*.yml(.yaml) to .github/workflows-disabled/ to neutralize them ahead of the org-wide GitHub Actions enablement. Restore via the re-enable-workflow process when a workflow is intentionally re-enabled. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
normprovost
approved these changes
Jun 3, 2026
normprovost
left a comment
normprovost
left a comment
There was a problem hiding this comment.
Verified: pure rename of .github/workflows -> .github/workflows-disabled (8 files, no content changes). Auto-approved.
zilleeizad-inter
added a commit
that referenced
this pull request
Jul 23, 2026
The CI/CD table describes intended behavior, but `.github/workflows/` doesn't exist on main — every workflow moved to `workflows-disabled/` as part of PR #536 (org-wide GitHub Actions enablement migration, 2026-06-03), and FERN_TOKEN / FERN_NPM_TOKEN were removed after the 2026-05-01 Fern token incident. Restoration is a separate operation gated on both the org migration and secret re-provisioning. Adds a leading note above the table so readers know the schedule column is aspirational until re-enablement.
zilleeizad-inter
added a commit
that referenced
this pull request
Jul 24, 2026
* chore: migrate from npm to pnpm with supply chain hardening Team: Integration Capabilities * chore: pin fern-api@5.65.3 to work around pnpm dist-tags gap pnpm's global install has no fallback when a registry manifest lacks dist-tags, and Intercom's Socket Firewall proxy serves the fern-api manifest without them, so `pnpm add -g fern-api` (unpinned) fails with ERR_PNPM_NO_MATCHING_VERSION. Pinning bypasses `latest` resolution. Upstream: pnpm/pnpm#5564, pnpm/pnpm#9944 (both open). * Remove unreachable stale-node_modules branch in preinstall guard pnpm's preinstall lifecycle fires AFTER pnpm relayouts node_modules (creates .pnpm/ and moves any npm-installed dirs to .ignored_<name>/), so the guard's `!fs.existsSync('node_modules/.pnpm')` check is always false by the time it runs. The branch is dead code under `pnpm install`. The wrong-package-manager path above already catches the common failure mode (a contributor running `npm install`), so nothing else is needed. Verified by instrumenting the script and running each install path. * Document `pnpm setup` pre-req before global installs On a fresh macOS shell, `pnpm add -g <pkg>` errors with `ERR_PNPM_NO_GLOBAL_BIN_DIR` because PNPM_HOME isn't wired into PATH yet. This trips up anyone regenerating an SDK from a clean clone — including Fern-support engineers. Document the one-time `pnpm setup` step in both the internal Development runbook (CLAUDE.md) and the external CONTRIBUTING guide. * Note that all CI workflows are currently disabled The CI/CD table describes intended behavior, but `.github/workflows/` doesn't exist on main — every workflow moved to `workflows-disabled/` as part of PR #536 (org-wide GitHub Actions enablement migration, 2026-06-03), and FERN_TOKEN / FERN_NPM_TOKEN were removed after the 2026-05-01 Fern token incident. Restoration is a separate operation gated on both the org migration and secret re-provisioning. Adds a leading note above the table so readers know the schedule column is aspirational until re-enablement. * Drop success-path pnpm-install telemetry The `pnpm-install` telemetry event fired on every successful install forever, not just during the migration window — it would keep sending per-engineer / per-repo data to Honeycomb long after the org-wide pnpm rollout completed, polluting the dataset with steady-state noise. Rollout progress can be inferred from the ABSENCE of `wrong-package-manager` events over time, so no substitute signal is needed. The failure-path telemetry (`wrong-package-manager`) remains in place — that's where the interesting signal lives. * chore: remove check-package-manager preinstall guard Drops scripts/check-package-manager.js and its package.json preinstall hook. The guard emitted install-time telemetry to an external endpoint, which is out of place in a public repo and unnecessary for the pnpm migration itself. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: drop workflow-status note from CLAUDE.md CI/CD section Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: drop pnpm setup note from CLAUDE.md and CONTRIBUTING.md Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: drop fern-api pin rationale note from CLAUDE.md Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: note pnpm setup pre-req for global bin dir Fresh machines without PNPM_HOME configured hit ERR_PNPM_NO_GLOBAL_BIN_DIR on pnpm add -g. Add the one-time pnpm setup step in front of the fern-api install so external contributors following CONTRIBUTING.md don't trip on it. --------- Co-authored-by: Vedran Zoricic <vedran.zoricic@intercom.io> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Zille Eizad <zille.eizad@intercom.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
As part of an org-wide GitHub Actions enablement migration, workflow files are being moved to
.github/workflows-disabled/to prevent them from triggering automatically until each workflow has been reviewed and approved for production use.How?
All 8 workflow files are relocated from
.github/workflows/to.github/workflows-disabled/— no workflow logic is changed. To re-enable a specific workflow later, move its file back into.github/workflows/following the standard re-enable safety review.Generated with Claude Code