Repository navigation
fix(deps): update dependency python-ulid to v4 - #371
Open
dreadnode-renovate-bot[bot] wants to merge 1 commit into
Open
dreadnode-renovate-bot[bot] wants to merge 1 commit into
dreadnode-renovate-bot[bot] wants to merge 1 commit into
Conversation
dreadnode-renovate-bot
Bot
force-pushed
the
renovate/python-ulid-4.x
branch
from
October 28, 2026 00:21
b4eef7a to
1228b26
Compare
Contributor
Author
|
dreadnode-renovate-bot
Bot
force-pushed
the
renovate/python-ulid-4.x
branch
2 times, most recently
from
November 11, 2026 00:21
1513109 to
0e5d471
Compare
| datasource | package | from | to | | ---------- | ----------- | ----- | ----- | | pypi | python-ulid | 3.1.0 | 4.2.0 |
dreadnode-renovate-bot
Bot
force-pushed
the
renovate/python-ulid-4.x
branch
from
November 18, 2026 00:21
0e5d471 to
977093e
Compare
This branch has not been deployed
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.
This PR contains the following updates:
>=3.0.0,<4.0.0→>=4.2.0,<4.3.0Release Notes
mdomke/python-ulid (python-ulid)
v4.2.0Compare Source
Added
.ULIDconstructor now accepts :class:bytesand bytes-like values (bytearrayand
memoryview), which are stored as immutable :class:bytes. A 16-character string or aninteger was previously accepted and produced an object whose
str()failed or that wasunhashable, so other types now raise :exc:
TypeError@KuljeetSinghXDA <https://github.com/KuljeetSinghXDA>_.dict,floator an out-of-rangeintnow raisespydantic.ValidationErrorinstead of leaking :exc:TypeErroror:exc:
OverflowError@KuljeetSinghXDA <https://github.com/KuljeetSinghXDA>_..ULID.parsenow treats any integer in the unsigned 128-bit range as a full ULIDinteger, instead of guessing from the number of decimal digits. Previously only integers with
exactly 37 digits were accepted, so
ULID.parse(int(ulid))failed for most ULIDs@KuljeetSinghXDA <https://github.com/KuljeetSinghXDA>_..ULID.from_datetimeand :meth:.ULID.from_timestampno longer land one millisecond earlywhen a value on an exact millisecond multiplies to just below that integer as a float
@arieleven <https://github.com/arieleven>_..ULID.from_datetimeand :meth:.ULID.from_timestampraise a :exc:ValueErrorfor valuesbefore the Unix epoch instead of a bare :exc:
OverflowError..ULID.from_intraises a :exc:ValueErrorfor integers outside the unsigned 128-bitrange instead of a bare :exc:
OverflowError.ulidcommand line tool reports invalid input as a short error message with exit status2 instead of a Python traceback.
import ulidno longer fails when the package metadata is missing, e.g. in applications frozenwith cx_Freeze or PyInstaller. The version is now written into the package at build time.
v4.1.0Compare Source
Changed
ULID.from_uuidv7to :meth:.ULID.from_uuid7for naming symmetry with:meth:
.ULID.to_uuid7, correcting an inconsistency introduced in 3.2.0.v4.0.1Compare Source
Changed
ULID.from_uuidv7toULID.from_uuid7for naming symmetry withULID.to_uuid7, correcting an inconsistency introduced in3.2.0.For the full
4.0.0feature set (the newULIDGenerator, monotonicity policies, anddefault_generator), see the 4.0.0 release.Full changelog: mdomke/python-ulid@4.0.0...4.0.1
v4.0.0Compare Source
.. warning::
Breaking change: the
ValueProviderclass and theULID.providerclass attributehave been removed. ULID generation is now handled by the new :class:
.ULIDGeneratortogetherwith pluggable monotonicity policies. To customize generation, construct a
:class:
.ULIDGenerator(optionally with a custom clock, randomness source, or policy) andeither call its
generate()method or assign it toulid.default_generator.Added
ValueProviderclass and theULID.providerattribute in favour of:class:
.ULIDGeneratorand the monotonicity policies. Code that replacedULID.providerorsubclassed
ValueProvidermust migrate to a custom :class:.ULIDGeneratorassigned toulid.default_generator.validate_typedecorator. TheULID.from_*constructors still raiseTypeErrorfor arguments of the wrong type, so runtime behaviour is unchanged.v3.2.1Compare Source
Fixed
ULID.to_uuid7andULID.from_uuidv7)@pirate <https://github.com/pirate>_.--uuid7option to the CLI'sshowcommand to convert and output a ULID as anRFC 4122 compliant UUIDv7.
Changed
@propertyto@cached_property@WH-2099 <https://github.com/WH-2099>_.incrementing the randomness component by 1 bit. This process is descrbied in the
spec <https://github.com/ulid/spec/blob/master/README.md#monotonicity>_.Fixed
TypeErrorinstead ofValueErrorif constructor is called with value of wrong type.rufflinter rules and switch tohatch fmt.Added
.ULID.milliseconds@tsugumi-sys <https://github.com/tsugumi-sys>_.v3.2.0Compare Source
Added
ULID.to_uuid7andULID.from_uuidv7) @pirate.--uuid7option to the CLI'sshowcommand to convert and output a ULID as an RFC 4122 compliant UUIDv7.Changed
typing-extensionsonly when running on Python < 3.11 @musicinmybrain.uvandpoethepoet.Fixed
uvduring synchronization @jaseemabid.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.