Skip to main content
https://badge.fury.io/py/galaxy-release-utils.svg

Overview

Scripts to create new Galaxy releases.

Development

Tests can be executed with tox.

Release Checklist

  • Update HISTORY.rst

  • Update version number in setup.cfg

  • Run make dist

  • Tag a new version and create a release from the GitHub interface

History

0.4.2 (03-08-2026)

Commit-to-pull-request lookups are now batched through GraphQL and run concurrently, reducing large release runs from thousands of REST requests to a few dozen queries.

Meta-package dependency generation now supports both static PEP 621 metadata and the transitional setup.cfg layout, and ignores blank lines, comments, and pip options when assembling dependencies.

0.4.1 (02-08-2026)

Galaxy’s dev branch moved package metadata to PEP 621 pyproject.toml. Merging a release branch forward, and building packages from the migrated tree, both died reading setup.cfg. Either file is now accepted, and the forward merge resolves the setup.cfg delete/modify conflict that the move introduces.

Anyone releasing from a branch that still uses setup.cfg is unaffected.

0.4.0 (30-07-2026)

Breaking change: --release-config and the {version}_release.yml config file are gone. The release date now comes from the due date of the milestone naming the release, and the previous and next versions from its neighbouring milestones, so create-changelog and check-blocking-prs no longer need dates passed to them. Pass --owner/--repo to work against a fork, and --release-date, --next-version or --previous-version to override what the milestones say. --freeze-date remains required by create-release-issue, since no milestone records it.

0.3.4 (30-07-2026)

0.3.3 (22-05-2026)

0.3.2 (20-01-2026)

0.3.1 (01-08-2025)

0.3.0 (20-06-2025)

0.2.0 (02-12-2024)

0.1.11 (20-05-2024)

0.1.9 (02-05-2024)

0.1.8 (02-05-2024)

0.1.7 (21-02-2024)

0.1.6 (14-02-2024)

0.1.5 (14-09-2023)

  • Bootstrap history fixes for regenerating existing docs

0.1.4 (30-06-2023)

  • Skip empty prerelease changelog when parsing changelog

0.1.3 (28-06-2023)

  • Add step/checkbox on updating db revision identifier

  • Bootstrap history fixes

0.1.2 (12-06-2023)

  • Fix isinstance assertion

0.1.1 (12-06-2023)

  • Add simplified makefile, development instruction

  • Fix project description

0.1.0 (12-06-2023)

  • Initial import from the Galaxy codebase

Metadata

Release files for galaxy-release-util 0.4.2

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-release-util 0.4.2
File Size Uploaded
galaxy_release_util-0.4.2.tar.gz 41.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for galaxy-release-util 0.4.2
File Interpreter ABI Platform
galaxy_release_util-0.4.2-py3-none-any.whl Python 3 none any Details

Total release size: 74.4 kB

Release files / galaxy_release_util-0.4.2.tar.gz

Download URL galaxy_release_util-0.4.2.tar.gz
Size 41.6 kB
Tags Source
SHA-256 checksum
How to use checksums
c1fa409e48fd78ccd6a82d9b38d7d54e7ee5b1cc05f4d59eca22fb5f289f93ae
BLAKE2b-256 checksum
How to use checksums
5f169e6c3073bbb8560b455dc5c4213c4b7eea4053b408473df42a319587d3f2
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 Aug 3, 2026.

Transparency log

Release files / galaxy_release_util-0.4.2-py3-none-any.whl

Download URL galaxy_release_util-0.4.2-py3-none-any.whl
Size 32.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d0af25ee5a3d07d0469f78a23acac448bce29d7cd2b9aedc2343821ed23ab7fb
BLAKE2b-256 checksum
How to use checksums
323b13ab0f0639bf418502eabc28f1e65c11f190849d280190cdbf41c2b09cfb
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 Aug 3, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.2 This release

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.11

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

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