MySQL 8.4 Upgrade Lint (RDS MySQL 8.0)
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
MySQL upgrade 8.0 → 8.4: finds the SQL, my.cnf and parameter-group lines that MySQL 8.4 removed, with the fix on each line
Install
mysql84-upgrade-blocker-lint file
Node 18+. The same 34 rules as the VS Code extension, from a terminal or CI.
Free
- Lint the open .sql, .cnf, .ini or .tf file against 34 MySQL 8.4 removals, with the line number and the fix on every finding, in VS Code or the web page, no key.
--ruleslists every rule
With a licence ($29 once)
- Scan every migration, my.cnf and parameter group in the workspace at once and export one upgrade-blocker report (Markdown + CSV) to attach to the upgrade ticket.
mysql84-upgrade-blocker-lint --dir ./templates --report html --out report.html
AWS has billed RDS for MySQL 8.0 Extended Support since 1 August 2026 at $0.100 per vCPU-hour (US East Ohio): $7,008 a year for one 8-vCPU instance running 8,760 hours.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "mysql84-upgrade-blocker-lint": { "command": "mysql84-upgrade-blocker-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: MySQL 8.4 Upgrade Lint (RDS MySQL 8.0)
run: pip install rulestamp-mysql84-upgrade-blocker-lint && mysql84-upgrade-blocker-lint --dir . --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 rulestamp-mysql84-upgrade-blocker-lint
mysql84-upgrade-blocker-lint --help
Metadata
Release files for rulestamp-mysql84-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 |
|---|---|---|---|---|
| rulestamp_mysql84_upgrade_blocker_lint-1.0.1.tar.gz | 16.7 kB | Without provenance | Details for rulestamp_mysql84_upgrade_blocker_lint-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_mysql84_upgrade_blocker_lint-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_mysql84_upgrade_blocker_lint-1.0.1-py3-none-any.whl |
Total release size: 35.5 kB
Release files / rulestamp_mysql84_upgrade_blocker_lint-1.0.1.tar.gz
| Download URL | rulestamp_mysql84_upgrade_blocker_lint-1.0.1.tar.gz |
|---|---|
| Size | 16.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56460a6d5a5bdb064aa06871aac6071dae40d90bf71d6b9eefb27b13a4fbeb12
|
|
BLAKE2b-256 checksum How to use checksums |
a175dc41ff49d5a4e6688688408c0f98391781a1e27bfdeb38cbfb1fd1c09f57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_mysql84_upgrade_blocker_lint-1.0.1-py3-none-any.whl
| Download URL | rulestamp_mysql84_upgrade_blocker_lint-1.0.1-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1adf116ce61d1c093321828d76ba7055dac315875842ff429a7da7cf52fb6c83
|
|
BLAKE2b-256 checksum How to use checksums |
9147c1870e1c3011991c86d487eb7c9bcc0f434615216e82c13bc83fbf953846
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-mysql84-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.