Skip to content

chore(release): 0.16.1#244

Merged
pratyush618 merged 2 commits into
masterfrom
chore/release-0.16.1
Jun 11, 2026
Merged

chore(release): 0.16.1#244
pratyush618 merged 2 commits into
masterfrom
chore/release-0.16.1

Conversation

@pratyush618

@pratyush618 pratyush618 commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

Changes since 0.16.0

  • PyPI publish pre-check with SHA-256 hash comparison (skip upload when already present)
  • PEP 639 compatibility (twine check without --strict)
  • Timeout guards on PyPI API calls and verification curl

Summary by CodeRabbit

  • Chores
    • Bumped package version to 0.16.1 across the project and updated the release badge/version constants.
  • Bug Fixes
    • Skip redundant PyPI uploads via a pre-check; relax twine strictness and pin compatibility.
    • Add timeouts for PyPI calls and a dashboard artifact download retry with CLI fallback.
  • Documentation
    • Added 0.16.1 changelog entry describing these fixes.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6cacb557-91ff-4b9d-afaa-d093d9c4926a

📥 Commits

Reviewing files that changed from the base of the PR and between 314bc89 and 96eccf8.

📒 Files selected for processing (3)
  • .github/actions/download-dashboard/action.yml
  • .github/workflows/publish.yml
  • docs/content/docs/more/changelog.mdx
✅ Files skipped from review due to trivial changes (1)
  • docs/content/docs/more/changelog.mdx

📝 Walkthrough

Walkthrough

This pull request performs a coordinated version bump from 0.16.0 to 0.16.1 across Rust crates and the Python package, adds a reusable dashboard-download composite GitHub Action, updates publish workflow jobs to use that action, and adds a 0.16.1 changelog entry documenting publish workflow hardening.

Changes

Version 0.16.1 Release

Layer / File(s) Summary
Version bumps across crate manifests and constants
crates/taskito-async/Cargo.toml, crates/taskito-core/Cargo.toml, crates/taskito-mesh/Cargo.toml, crates/taskito-python/Cargo.toml, crates/taskito-workflows/Cargo.toml, pyproject.toml, py_src/taskito/__init__.py, docs/src/lib/release.ts
Version fields updated from 0.16.00.16.1 across Rust crate manifests, Python project metadata, the package __version__ fallback, and the docs release constant.
Composite action: download-dashboard
.github/actions/download-dashboard/action.yml
Adds a composite GitHub Action that downloads the dashboard-dist artifact into py_src/taskito/static/dashboard, retries with gh CLI up to three times on failure, and verifies index.html exists.
Publish workflow uses composite action
.github/workflows/publish.yml
Replaces direct actions/download-artifact@v8 calls and explicit index.html checks with calls to ./.github/actions/download-dashboard in Linux (glibc), musl, macOS, Windows, and sdist jobs.
Changelog documentation for 0.16.1
docs/content/docs/more/changelog.mdx
New 0.16.1 changelog entry describing publish workflow hardening: PyPI pre-checks, twine/PEP 639 adjustments, timeouts, and dashboard artifact download retry with gh fallback.

Sequence Diagram

sequenceDiagram
  participant Runner as GitHub Runner
  participant Action as download-dashboard
  participant Download as actions/download-artifact@v8
  participant GHCLI as gh CLI
  participant FS as FileSystem
  Runner->>Action: invoke composite action
  Action->>Download: attempt download dashboard-dist -> py_src/taskito/static/dashboard
  alt download succeeds
    Download->>FS: write files (index.html)
    Action->>Runner: verify index.html exists -> success
  else download fails
    Action->>GHCLI: retry download up to 3 times (gh run download ...)
    GHCLI->>FS: write files on success
    GHCLI->>Action: return status
    Action->>Runner: verify index.html exists -> success or fail
  end
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • ByteVeda/taskito#243: Related adjustments to PyPI publish/validation logic and twine handling in the publish workflow.
  • ByteVeda/taskito#241: Related changes adding a PyPI pre-publish check to skip uploads when artifacts already exist.
  • ByteVeda/taskito#222: Prior release/version bump touching py_src/taskito/__init__.py __version__ fallback and manifest version updates.

Suggested labels

ci

Poem

🐰 A hop and a bump, the versions align,
0.16.1 now sits snug in the line,
Dashboards retried with a clever fallback,
Twine checks tuned so uploads don't crack,
Hooray — a small hop, a stable track!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(release): 0.16.1' clearly and concisely summarizes the main change: a version bump to 0.16.1 across the entire project.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-0.16.1

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added the ci label Jun 11, 2026
@pratyush618
pratyush618 merged commit 5dbc597 into master Jun 11, 2026
25 checks passed
@pratyush618
pratyush618 deleted the chore/release-0.16.1 branch June 11, 2026 04:56
@coderabbitai coderabbitai Bot mentioned this pull request Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant