chore: bump baton-github v0.2.12 → v0.2.13

[madison-c-evans]

Summary

• Bump baton-github from v0.2.12 to v0.2.13
• Fixes enterprise SAML emails not syncing (found during e2e validation on sandbox)

Root cause

The SDK calls ResourceSyncers() before Validate(), so the enterpriseLicensesAvailable gate was always false — enterprises were never passed to builders. v0.2.13 removes the gate and always passes enterprises through.

Test plan

• Verified locally with go mod replace — SAML emails sync correctly
• CI passes

🤖 Generated with Claude Code

[linear]

CXH-1180 GitHub: Support syncing emails when SAML is configured at Enterprise level

[github-actions]

Claude finished @madison-c-evans's task in 38s —— View job

---

PR Review: chore: bump baton-github v0.2.12 → v0.2.13

• Gather context
• Review changes
• Post review

---

Verdict: Looks good ✅

This is a clean, well-scoped fix. The change removes the enterpriseLicensesAvailable gate that was always false when ResourceSyncers() ran (because the SDK calls it before Validate()), meaning enterprise SAML emails and enterprise role sync were silently disabled.

What changed (4 files, +9/−22):

1. Removed the enterpriseLicensesAvailable field from the GitHub struct — it was dead state since ResourceSyncers() always ran before Validate() could set it to true.
2. ResourceSyncers() now passes gh.enterprises directly to userBuilder and enterpriseRoleBuilder instead of going through the gated activeEnterprises local variable.
3. Validate() / validateAppCredentials() still probe the consumed-licenses API but now only log a warning instead of gating functionality. The log message was updated from "will be skipped" → "may fail at sync time", which correctly reflects the new behavior.
4. go.mod / go.sum / vendor/modules.txt — standard version bump bookkeeping.

No concerns:

• The fix is minimal and directly addresses the root cause (ordering mismatch between ResourceSyncers and Validate).
• The Validate probe is kept as a useful diagnostic log without gating behavior.
• No new dependencies or API surface changes.

---