irelease

GitHub repo size

Release your library by using the command: irelease or pyrelease

Star this repo if you like it! ⭐️

Introduction

irelease is Python package that will help to release your python package on both github and pypi. A new release of your package is created by taking the following steps:

Extract the version from the init.py file
Remove old build directories such as dist, build and x.egg-info
Git pull (to make sure all is up to date)
Get latest release version at github

Check if the local (current) version is newer then the latest github release.

 1. Make new wheel, build and install package
 2. Set tag to newest version
 3. Push to git
 4. Upload to pypi (credentials for pypi required)

Installation

Install irelease from PyPI (recommended). irelease is compatible with Python 3.6+ and runs on Linux, MacOS X and Windows.
It is distributed under the MIT license.

Quick Start

pip install irelease

Alternatively, install irelease from the GitHub source:

git clone https://github.com/erdogant/irelease.git
cd irelease
python setup.py install

Run irelease

Go to the directory where the package is you want to release and simply run release:

$ irelease

The following arguments are availble:

# Github name
irelease -u <githubname>

# Package name your want to release
irelease -p <packagename>

# Removing local builds:
# 1: Yes
# 0: No
irelease -c 1

# Verbosity messages:
# 0: No messages
# 1: Error only
# 2: Warnings and above
# 3: Regular messages and above
# 4: Debug and above
# 5: Trace and above
irelease -v 5

# Twine path for to irelease at pypi. This is automatically determined if standard installation is performed.
irelease -t 'C://<username>/AppData/Roaming/Python/Python36/Scripts/twine.exe'

Example:

Your package to-be-published must have the correct structure. At least these files and folders are expected:

    <any_dirname>/
    ├── <package_dir>/
    │   ├── __init__.py
    │   ├── package_name.py
    │   ├── ...
    ├── .gitignore
    ├── LICENSE
    ├── README.md
    ├── requirements.txt
    ├── setup.py
    └── ...

Example: releasing bnlearn package.

    bnlearn/
    ├── bnlearn/
    │   ├── __init__.py
    │   ├── bnlearn.py
    ├── .gitignore
    ├── LICENSE
    ├── README.md
    ├── requirements.txt
    ├── setup.py

Go to your destination dir and run release:

$ irelease

release with your specified arguments

# Package can be specified:
$ bnlearn>irelease -p bnlearn

# Username can be specified:
$ bnlearn>irelease -u erdogant

# Cleaning of previous builds in directory can be disabled
$ bnlearn>irelease -c 0

Do not forget to enter some release information on github and mark your release number:

Maintainer

Erdogan Taskesen, GitHub: erdogant
Contributions are welcome.
Yes! This library is entirely free, but it runs on coffee! :) Feel free to support with a Coffee.

Release files for irelease 1.4.0

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

Source distribution (sdist)

Source distribution for irelease 1.4.0
File	Size	Uploaded
irelease-1.4.0.tar.gz	15.6 kB	Sep 23, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for irelease 1.4.0
File	Interpreter	ABI	Platform	Reset
irelease-1.4.0-py3-none-any.whl 14.3 kB Sep 23, 2026	Python 3	none	any	Details

Total release size: 29.9 kB

Release files / irelease-1.4.0.tar.gz

Download URL	irelease-1.4.0.tar.gz
Size	15.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`c4671086a93c818e0a027c255671e50db2e3e59c4c10a834ab5c4958f20aa6a6`
BLAKE2b-256 checksum How to use checksums	`228189f01178c41d29b9dfe008a9b9ef659759ab853625c44bca73514eff4c0c`
Upload date	Sep 23, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/erdogant/irelease
Publishing commit: github.com/erdogant/irelease/tree/c1f4588d37d872df460f75d15e987a6acc8a7eb9

Workflow

Publishing configuration: github.com/erdogant/irelease/blob/c1f4588d37d872df460f75d15e987a6acc8a7eb9/.github/workflows/release.yml
Publishing logs: github.com/erdogant/irelease/actions/runs/35886642534/attempts/1

Artifact

Subject: irelease-1.4.0.tar.gz
SHA-256 checksum: c4671086a93c818e0a027c255671e50db2e3e59c4c10a834ab5c4958f20aa6a6 Verifying attestations

Release files / irelease-1.4.0-py3-none-any.whl

Download URL	irelease-1.4.0-py3-none-any.whl
Size	14.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`a26cadb42434c632cb0347858e3f4543e5ad4738965b817770c8e5819bc0f9fa`
BLAKE2b-256 checksum How to use checksums	`0fe245e4677b1041d3f9d9dbdf1c9ddfe53773f8146a15701832c3547178ba27`
Upload date	Sep 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/erdogant/irelease
Publishing commit: github.com/erdogant/irelease/tree/c1f4588d37d872df460f75d15e987a6acc8a7eb9

Workflow

Publishing configuration: github.com/erdogant/irelease/blob/c1f4588d37d872df460f75d15e987a6acc8a7eb9/.github/workflows/release.yml
Publishing logs: github.com/erdogant/irelease/actions/runs/35886642534/attempts/1

Artifact

Subject: irelease-1.4.0-py3-none-any.whl
SHA-256 checksum: a26cadb42434c632cb0347858e3f4543e5ad4738965b817770c8e5819bc0f9fa Verifying attestations