Linux workstation

Upstream software project

flask-migrate

SQLAlchemy database migrations for Flask applications using Alembic

About flask-migrate

SQLAlchemy database migrations for Flask applications using Alembic

This project links 9 native package records across 6 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

flask-migrate repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.flask-migrate: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
flask-migrate
Publisher
Not authoritatively mapped
Native package records
9
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-tumbleweed
License expression
MIT
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Flask-Migrate is an extension that handles SQLAlchemy database migrations for Flask applications using Alembic. The database operations are provided as command line arguments for Flask-Script.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. flask-migrate-doc

    Debian 12 (Bookworm) / doc / source flask-migrate

    4.0.4-1

    SQLAlchemy migrations for Flask using Alembic and Python 3 (Documentation)

    allbookworm
  2. python3-flask-migrate

    Debian 12 (Bookworm) / python / source flask-migrate

    4.0.4-1

    SQLAlchemy migrations for Flask using Alembic and Python 3

    allbookworm

Debian 13 (Trixie)

  1. flask-migrate-doc

    Debian 13 (Trixie) / doc / source flask-migrate

    4.1.0-1

    SQLAlchemy migrations for Flask using Alembic and Python 3 (Documentation)

    alltrixie
  2. python3-flask-migrate

    Debian 13 (Trixie) / python / source flask-migrate

    4.1.0-1

    SQLAlchemy migrations for Flask using Alembic and Python 3

    alltrixie

Fedora 43

  1. python3-flask-migrate

    Fedora 43 / Unspecified / source python-flask-migrate

    4.1.0-11.fc43

    SQLAlchemy database migrations for Flask applications using Alembic

    noarch43

Fedora 44

  1. python3-flask-migrate

    Fedora 44 / Unspecified / source python-flask-migrate

    4.1.0-13.fc44

    SQLAlchemy database migrations for Flask applications using Alembic

    noarch44

openSUSE Leap 15.6

  1. python311-Flask-Migrate

    openSUSE Leap 15.6 / Unspecified / source python-Flask-Migrate

    4.0.5-150600.1.2

    SQLAlchemy database migrations for Flask applications using Alembic

    noarchleap-15.6

openSUSE Tumbleweed

  1. python313-Flask-Migrate

    openSUSE Tumbleweed / Unspecified / source python-Flask-Migrate

    4.1.0-1.3

    SQLAlchemy database migrations for Flask applications using Alembic

    noarchtumbleweed
  2. python314-Flask-Migrate

    openSUSE Tumbleweed / Unspecified / source python-Flask-Migrate

    4.1.0-1.3

    SQLAlchemy database migrations for Flask applications using Alembic

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.