Repository navigation
chore(release): bump unirl to 0.2.0 - #553
Merged
celve merged 2 commits intoOct 6, 2026
Merged
Conversation
0.1.0 is the initial release already on PyPI. main has since gained features and changes that are not drop-in, so the next release is a minor bump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
unirl.__version__from0.1.0to0.2.0.pyproject.tomltakes the package version from this attribute.unirl0.1.0 has been on PyPI since 2026-06-09, built from the initial-release code, and PyPI never accepts a version twice.mainis now 293 commits past that build, including 116featcommits and several changes that are not drop-in, so the next release should be0.2.0rather than0.1.1:DIFFRL_*environment variables and the old socket/lock/shm paths are no longer recognized (refactor: rename residual DiffRL identifiers to UniRL #498).RolloutReq.stage_configbecametask_config(refactor(types): rename RolloutReq.stage_config to task_config #255) and then moved ontoPart.control(refactor(types): retire stage_config/task_config onto Part.control #263).ComposedSamplingParams(refactor(sampling): modality-keyed sampling dict in RolloutReq, drop ComposedSamplingParams #70) and the compatibility aliases (refactor: delete repo-internal compatibility aliases and re-export facades #366) were removed.>=4.41→>=5.12,<5.13, torch 2.11 → 2.13, vLLM / vLLM-Omni 0.20 → 0.28 (CUDA 12.9 → 13), and SGLang 0.5.12.post1 → 0.5.19.The initial commit (
a1f8596) is now taggedv0.1.0. Its package code is identical to what PyPI's 0.1.0 was built from. After this merges, its squash commit will be taggedv0.2.0.Related Issue
N/A — tracked internally.
Test Plan
uv build --sdist --wheel→unirl-0.2.0.tar.gzandunirl-0.2.0-py3-none-any.whl. The wheel'sMETADATAreadsVersion: 0.2.0.git grep -n -F '0.1.0' -- ':!unirl-reward-service'→ no matches, so the old version string appears nowhere else.SKIP=no-commit-to-branch pre-commit run --files unirl/__init__.py→ all hooks pass.Compatibility / Risk
This changes version metadata only.
pyproject.tomlis the only reader ofunirl.__version__; the runtime version checks inunirl/all query other distributions.unirl-reward-serviceis versioned separately, with its ownpyproject.tomlandCHANGELOG.md, and stays at 0.1.0.Reviewer Notes
gh pr list --state open --search '__version__ OR "bump version" OR "0.2.0" in:title,body'returns nothing, and the repo has no GitHub releases.Checklist