Skip to content

[v3-3-test] Add upgrade-fab-provider skill and FAB contributing doc (#69729)#69756

Merged
shahar1 merged 1 commit into
v3-3-testfrom
backport-621192d-v3-3-test
Jul 11, 2026
Merged

[v3-3-test] Add upgrade-fab-provider skill and FAB contributing doc (#69729)#69756
shahar1 merged 1 commit into
v3-3-testfrom
backport-621192d-v3-3-test

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Upgrading the pinned Flask-AppBuilder dependency is deceptively involved:
the FAB provider vendors and subclasses large parts of FAB's security
manager, so a bump must be reconciled against that vendored code, the
alignment-test tripwire, and the generated provider README. Capturing the
verified procedure as a skill — and a matching providers/fab/CONTRIBUTING.rst
that points contributors at it and records past bumps — lets future FAB
upgrades follow the same checklist instead of rediscovering it each time.
The skill lives vendor-neutrally in .agents/skills with .claude and .github
relays, matching the repository's existing skill layout.
(cherry picked from commit 621192d)

Co-authored-by: Jarek Potiuk jarek@potiuk.com

…69729)

Upgrading the pinned Flask-AppBuilder dependency is deceptively involved:
the FAB provider vendors and subclasses large parts of FAB's security
manager, so a bump must be reconciled against that vendored code, the
alignment-test tripwire, and the generated provider README. Capturing the
verified procedure as a skill — and a matching providers/fab/CONTRIBUTING.rst
that points contributors at it and records past bumps — lets future FAB
upgrades follow the same checklist instead of rediscovering it each time.
The skill lives vendor-neutrally in .agents/skills with .claude and .github
relays, matching the repository's existing skill layout.
(cherry picked from commit 621192d)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@shahar1
shahar1 merged commit 2ad2e4f into v3-3-test Jul 11, 2026
88 of 97 checks passed
@shahar1
shahar1 deleted the backport-621192d-v3-3-test branch July 11, 2026 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants