chore(release): prepare v0.4.0#136
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Prepares the repository for the v0.4.0 release, aligning workspace/crate versions and documenting the release notes for the new pluggable HTTP transport abstraction introduced in #135.
Changes:
- Bump workspace version to
0.4.0and update dependent crate versions in the lockfile. - Update
fetchkit-clito depend onfetchkit v0.4.0. - Add
0.4.0release notes and update changelog comparison links.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| crates/fetchkit-cli/Cargo.toml | Updates the fetchkit dependency version to 0.4.0 for the CLI crate. |
| CHANGELOG.md | Adds the 0.4.0 entry (highlights + breaking changes) and updates comparison links. |
| Cargo.toml | Bumps the workspace package version to 0.4.0. |
| Cargo.lock | Updates locked workspace crate versions to 0.4.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Release v0.4.0
Breaking minor release: pluggable HTTP transport abstraction (#135).
Why 0.4.0 (not 0.3.1)
FetchOptionsgained a publictransportfield and it is an exhaustive pub struct — formally breaking for exhaustive struct-literal construction. Cargo auto-upgrades within^0.3, so the breaking change must move out of the 0.3.x range.Changelog excerpt
Highlights
FetchOptions::transport/ToolBuilder::transport); fetchkit keeps URL validation, DNS pinning, redirect following, signing, body caps. Default unchanged (ReqwestTransport).max_body_size.Breaking Changes
FetchOptionsnew publictransportfield — add it or use..Default::default().FetchOptions/Tool/ToolBuilderDebug impls are now manual.Verification
cargo fmt --all -- --check✓cargo clippy --workspace --all-targets -- -D warnings✓cargo test --workspace✓ (all suites)RUSTDOCFLAGS="-D warnings" cargo doc --workspace --no-deps✓cargo build --workspace --exclude fetchkit-python --release✓After merge, release.yml creates the GitHub Release
v0.4.0and dispatches publish.yml (fetchkit → fetchkit-cli, in order).