chore: retarget dependency automation to main

[estivate]

Problem

Dependabot and the SDK release workflow both target develop. The repository default branch is main, so automated dependency pull requests from either path use a stale base.

Solution

Remove the Dependabot target overrides and change the SDK workflow target from develop to main. Dependabot now uses the repository default branch. SDK release events create a main-infrahub-sdk-<version> branch and open the pull request against main.

Before and after

# Before
target-branch: develop
branch-name:
  - develop

# After
# Dependabot uses the repository default branch.
branch-name:
  - main

Scope

• Preserve the existing schedules, dependency groups, housekeeping labels, and SDK release triggers.
• Leave trigger-pr-develop.yml unchanged. Retiring the protected develop branch and its remaining CI references requires a separate cleanup.
• Change no Infrahub Sync product, CLI, or configuration behavior.

Validation

• uv sync --extra dev: passed.
• uv run invoke format: passed with no generated changes.
• uv run invoke lint: passed with the existing Pylint notices.
• Targeted YAML validation: passed; the SDK matrix contains main and no develop target.
• uv run infrahub-sync --help: passed.
• uv run infrahub-sync list --directory examples/: passed.
• Targeted generation reached the local Infrahub stack and stopped at the expected schema-availability check.
• The final diff contains the two Dependabot target removals and the SDK workflow target replacement.
• GitHub Actions run 31761890946: passed for exact head d28efb7 with no pending or failed checks.

Follow-up

After this merges:

• Close build(deps): bump the all group with 5 updates #154 and build(deps): bump actions/setup-node from 6 to 7 in the all group across 1 directory #163 because Dependabot generated them from develop.
• Allow Dependabot to regenerate equivalent updates from current main.
• Retire the protected develop branch and remove its remaining workflow references in a separate cleanup.
• Refresh uv.lock manually if the regenerated Python update does not include it.

🤖 Generated with OpenAI Codex

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d2cbf5af-fafd-4d66-abb8-288fa33caedf

📥 Commits

Reviewing files that changed from the base of the PR and between 3ea837e and d28efb7.

📒 Files selected for processing (1)

• .github/workflows/update-infrahub-sdk.yml

---

Walkthrough

Removed target-branch: develop from the GitHub Actions and pip Dependabot update entries. Changed the SDK update workflow matrix branch from develop to main. Scheduling, labels, and grouping configuration remain unchanged.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The changes do not implement the dependency updates required by issue #154 for structlog, pyarrow, invoke, ruff, and ty.	Update the dependency requirements listed in issue #154, or link this PR to an issue that covers retargeting Dependabot to main.
Out of Scope Changes check	⚠️ Warning	The branch retargeting changes are unrelated to the dependency version updates required by linked issue #154.	Move the branch retargeting changes to a separate PR, or update the linked issue to define this scope.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: retargeting dependency automation from develop to main.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying infrahub-sync with    Cloudflare Pages

Latest commit:	d28efb7
Status:	✅  Deploy successful!
Preview URL:	https://e41faafb.infrahub-sync.pages.dev
Branch Preview URL:	https://chore-dependabot-target-main.infrahub-sync.pages.dev

View logs

[estivate]

Administrative merge follow-up

An administrative override was considered after this PR remained without an approving review for three weeks. The override was not used.

The branch was rebased, independently checked for scope and semantic drift, and passed CI on exact head e205ef2. The final OpsMill ship gate nevertheless stopped the merge because the required independent approval remains outstanding.

PR #146 remains open. Branch protection was not changed or bypassed.

[estivate]

Review: Approve

Verified independently against the repo:

• Confirmed main is the actual default branch and the active development line — develop has had exactly one merge in recent history (build(deps): bump the all group with 8 updates #138), itself a dependabot GHA bump that never made it to main. That's a live example of the drift this PR fixes.
• .github/dependabot.yml: both target-branch: develop overrides removed, so Dependabot now falls back to the repo default (main).
• .github/workflows/update-infrahub-sdk.yml: matrix branch-name retargeted from develop to main. Checked the full file — no remaining develop references.
• trigger-pr-develop.yml intentionally left untouched, per the PR's stated scope — retiring the protected develop branch is a separate, larger change and shouldn't be bundled with this mechanical retarget.
• CI green on d28efb7, including action-lint and yaml-lint. No required-status-check contexts are configured on main, so review approval is the only remaining blocker.

Follow-ups (#154, #163 close-and-regenerate, eventual develop retirement) are accurately captured in the PR description. Nothing further needed from my side — good to merge once approved.

🤖 Generated with Claude Code