Aurora MySQL 5.7 to 8.0 Upgrade Blocker Lint
28 MySQL 8.0 removal rules for .sql, .cnf and Terraform, before Aurora MySQL v2 Extended Support year 3 on 1 Dec 2026
Install
aurora-mysql57-upgrade-blocker-lint file
Node 18+. The same 28 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the open .sql, .cnf or .tf file against all 28 MySQL 8.0 removal rules and shows every blocking line with its 8.0 replacement, free in the editor and in the browser. The sample dirty.sql gives 14 findings on 13 lines.
--ruleslists every rule
With a licence ($29 once)
- Scans the whole workspace (every migration, parameter group and Terraform module) in one run and exports a dated Markdown upgrade report you can attach to the change ticket.
@readystack/aurora-mysql57-upgrade-blocker-lint --dir ./templates --report html --out report.html
AWS Extended Support year 3: $0.200 per vCPU-hour in US East (Ohio) = $1,168 a month, $14,016 a year for one 8 vCPU instance
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "aurora-mysql57-upgrade-blocker-lint": { "command": "npx", "args": ["-y", "@readystack/aurora-mysql57-upgrade-blocker-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Aurora MySQL 5.7 to 8.0 Upgrade Blocker Lint
run: npx -y @readystack/aurora-mysql57-upgrade-blocker-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/aurora-mysql57-upgrade-blocker-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-aurora-mysql57-upgrade-blocker-lint
aurora-mysql57-upgrade-blocker-lint --help
Metadata
Release files for readystack-aurora-mysql57-upgrade-blocker-lint 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1.tar.gz | 13.2 kB | Without provenance | Details for readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1-py3-none-any.whl |
Total release size: 28.2 kB
Release files / readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1.tar.gz
| Download URL | readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9440997def52f1df6f147c1fb1f7cc8a44cd3b6c7db67b300bb3069b5571e66
|
|
BLAKE2b-256 checksum How to use checksums |
0d3986912f83844d1cfc798caff0def7f8c838da5867a72d0d27069b62f23cde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1-py3-none-any.whl
| Download URL | readystack_aurora_mysql57_upgrade_blocker_lint-1.0.1-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa62941977886ed1540cde65b29c5c1b26b68b6727ee602d81c9a2228ac98023
|
|
BLAKE2b-256 checksum How to use checksums |
50ff990ade4aecfc24250b5e43f4333feae5e3007cf4bb0507656f99672caf28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-aurora-mysql57-upgrade-blocker-lint 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.