Skip to main content

galaxy-tool-refactor-rules

Shared rule-metadata vocabulary for the Galaxy tool refactoring framework — a small, dependency-free "tier 0.5" package consumed by both higher tiers:

Tier Layer Package
0.5 rule metadata galaxy-tool-refactor-rules (this package)
1 parsing & validation galaxy-tool-source
2 structure galaxy-tool-codemod
3 formatting galaxy-tool-fmt
3.5 advisory checks galaxy-tool-lint
3.6 rule registry / rulesets galaxy-tool-refactor-registry
4 app / CLI galaxy-tool-refactor-cli

It provides:

  • galaxy_tool_refactor_rules.meta.RuleMeta — a frozen dataclass describing one GTR rule (code, summary, since, until, cite, order, detect_only, applies_to). A tier-3 formatter Rule, a tier-2 CodemodCommand, and a tier-3.5 CheckRule each carry a meta: ClassVar[RuleMeta], so the tiers share one registry vocabulary.
  • galaxy_tool_refactor_rules.violation.Violation — a frozen dataclass for a detect-phase finding (code, sourceline, xpath, message); the pure, lxml-free, read-only counterpart to the mutating tier-2 Change / tier-3 Edit.
  • galaxy_tool_refactor_rules.reference.render_rule_reference_table — a pure helper that renders (RuleMeta, tier) pairs as a GitHub-flavored markdown glossary table.

Why a separate package

The descriptor is the only thing the two tiers genuinely share — their behavioral bases differ (fmt yields lxml edits; codemod walks a cursor), so those stay in their own packages. Keeping RuleMeta here, with zero runtime dependencies, lets both fmt and codemod depend on it without depending on each other — preserving the tier independence documented in galaxy-tool-fmt/docs/decisions.md §D10. The extraction was anticipated in that package's §D1 ("a shared rule-engine package will be extracted only when a second consumer materialises"); the codemod tier is that consumer.

Install / test

uv sync   # from the workspace root
uv run --package galaxy-tool-refactor-rules pytest galaxy-tool-refactor-rules/tests/

Metadata

Release files for galaxy-tool-refactor-rules 0.3.9

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for galaxy-tool-refactor-rules 0.3.9
File Size Uploaded Provenance Actions
galaxy_tool_refactor_rules-0.3.9.tar.gz 13.3 kB With provenance Details for galaxy_tool_refactor_rules-0.3.9.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for galaxy-tool-refactor-rules 0.3.9
File Interpreter ABI Platform Actions
galaxy_tool_refactor_rules-0.3.9-py3-none-any.whl Python 3 none any Details for galaxy_tool_refactor_rules-0.3.9-py3-none-any.whl

Total release size: 22.1 kB

Release files / galaxy_tool_refactor_rules-0.3.9.tar.gz

Download URL galaxy_tool_refactor_rules-0.3.9.tar.gz
Size 13.3 kB
Tags Source
SHA-256 checksum
How to use checksums
b28bb53dfbbcf6446241cc67c0514e7259301b1933d749c385e878f5ed4534fe
BLAKE2b-256 checksum
How to use checksums
9edbebd59028f2111bcd35fbb8ead7958fc7edddac474419398bf60cf6c4f4d0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

Release files / galaxy_tool_refactor_rules-0.3.9-py3-none-any.whl

Download URL galaxy_tool_refactor_rules-0.3.9-py3-none-any.whl
Size 8.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aa2b774c78ec5eff1201ed896ab63c7a70af121bfbffbb66b555861cdcd8cfb5
BLAKE2b-256 checksum
How to use checksums
02d72c59c0816526ae10ba4ba24fb7fdeb8bfde614a38e7a8c2d2ca880242df8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

Security for galaxy-tool-refactor-rules 0.3.9

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for galaxy_tool_refactor_rules-0.3.9.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page