chore: bump 0.1.0 → 0.1.1#17
Merged
Merged
Conversation
Move the [Unreleased] section to [0.1.1] - 2026-05-10. Bump version in dagron-core, dagron-py, dagron-ui, pyproject.toml, and py_src/dagron/__init__.py. Add a Docs note for the Docusaurus → Fumadocs migration.
3 tasks
pratyush618
added a commit
that referenced
this pull request
May 9, 2026
uv.lock still pinned the editable dagron at 0.1.0 after #17 bumped pyproject.toml to 0.1.1. Refresh the lockfile so the working tree matches the published version.
pratyush618
added a commit
that referenced
this pull request
May 9, 2026
* fix(test): bump _delayed sleep so Windows clock tick doesn't drop nodes test_profile_linear_dag flaked on windows-latest because the per-node 10ms sleep is below the ~16ms granularity of Windows' time.monotonic. Nodes occasionally measured duration=0.0 and got excluded from the critical path. Bump the default to 50ms so every sleep crosses at least one timer tick. * chore: sync uv.lock with 0.1.1 version bump uv.lock still pinned the editable dagron at 0.1.0 after #17 bumped pyproject.toml to 0.1.1. Refresh the lockfile so the working tree matches the published version. * ci: bump pnpm/action-setup v4 → v6 (Node 24) GitHub deprecated Node 20 actions; v4 of pnpm/action-setup runs on Node 20. Bump to v6 which uses Node 24 natively. The remaining actions/cache@v4 warning is transitive from actions/setup-node and auto-resolves once @v6 picks up its v6.2+ patch (which already uses @actions/cache v5.0.1). The windows-latest notice is just informing about the May 12 default flip to windows-2025-vs2026. * ci: pin actions to major version only (no patch) Drop the v2.9.1 / v3.0.1 patch pins on Swatinem/rust-cache and pre-commit/action — major-only references auto-pick up bug fixes without manual bumps. * ci: keep pre-commit/action at v3.0.1 (no rolling v3 tag exists) That action only publishes full-semver tags (v3.0.0, v3.0.1); v3 isn't a ref so the previous bump broke the lint job with "Unable to resolve action pre-commit/action@v3". Swatinem/rust-cache and pnpm/action-setup do ship rolling major tags and stay at @v2 / @v6.
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
1 participant
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
Cuts the 0.1.1 release. The post-merge follow-up to #16 (typed-handle migration + uniqueness pillars + fumadocs docs).
[Unreleased]section inCHANGELOG.mdto[0.1.1] - 2026-05-10.version = "0.1.0"→"0.1.1"in:crates/dagron-core/Cargo.tomlcrates/dagron-py/Cargo.tomlcrates/dagron-ui/Cargo.tomlpyproject.tomlpy_src/dagron/__init__.py(__version__)Test plan
cargo check --workspace— cleanmaturin develop— builds wheel asdagron-0.1.1-cp312-abi3-linux_x86_64.whlpython -c "import dagron; print(dagron.__version__)"→0.1.1v0.1.1and let the publish workflow run