Migrate apache-steward framework adoption to Apache Magpie#67929
Merged
Conversation
The framework was renamed apache-steward -> Apache Magpie upstream (apache/airflow-steward apache#436-apache#440). This migrates the adoption to the new layout via the framework's pre-Magpie -> Magpie migration shim: - .apache-steward* -> .apache-magpie* (snapshot, committed lock, overrides dir) - committed setup-steward skill -> magpie-setup - framework symlinks re-prefixed to magpie-* (list-steward-skills -> magpie-list-skills) - .gitignore collapsed to a magpie-* glob with a magpie-setup negation - .pre-commit-config.yaml hook exclusions updated to the new paths - post-checkout hook + README/AGENTS references updated Use /magpie-setup for all framework operations from now on.
/magpie-setup upgrade refreshed the snapshot to airflow-steward main (09902844de, which includes apache#441) and re-copied the committed bootstrap: - adopt.md now carries the !/.../magpie-setup gitignore negation (apache#441) - drops the duplicate SPDX header the license hook had injected (the skill is excluded from that hook, so the framework's own header is canonical)
jscheffl
approved these changes
Jun 3, 2026
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker b947945 v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
1 task
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
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.
What
Migrates this repo's framework adoption from apache-steward to Apache Magpie, following the framework's upstream rename (apache/airflow-steward #436–#440) and driven by its built-in pre-Magpie → Magpie migration shim.
Renames
.apache-steward/(snapshot, gitignored).apache-magpie/.apache-steward.lock.apache-magpie.lock.apache-steward.local.lock(gitignored).apache-magpie.local.lock.apache-steward-overrides/.apache-magpie-overrides/setup-stewardskillmagpie-setupmagpie-*(list-steward-skills→magpie-list-skills)Adopter config updated
.gitignore— collapsed the per-family symlink lines into a singlemagpie-*glob, with a!/.../magpie-setupnegation so the committed bootstrap stays tracked..pre-commit-config.yaml— the hook exclusions that named.github/skills/setup-steward/and.apache-steward-overrides/now point at the magpie paths (otherwise the license / codespell / markdownlint / lychee hooks fail on the renamed committed skill)..git/hooks/post-checkoutcomment +README.md/AGENTS.mdreferences.From now on use
/magpie-setupfor all framework operations.Generated-by: Claude Code (Opus 4.8)