Skip to content

fix: bump ckb-types to minor version 1.2.0#5151

Closed
Copilot wants to merge 2 commits intorelease-plz-2026-03-12T07-03-54Zfrom
copilot/sub-pr-5140
Closed

fix: bump ckb-types to minor version 1.2.0#5151
Copilot wants to merge 2 commits intorelease-plz-2026-03-12T07-03-54Zfrom
copilot/sub-pr-5140

Conversation

Copy link
Contributor

Copilot AI commented Mar 20, 2026

What problem does this PR solve?

ckb-types was released as 1.1.1 (patch), but PR #5023 added a new public method OutPointError::out_point() — a backward-compatible API addition that requires a minor version bump per semver.

What is changed and how it works?

  • util/types/Cargo.toml: 1.1.11.2.0
  • util/types/CHANGELOG.md: Updated release header; reclassified entry from FixedAdded
  • Cargo.lock: Updated ckb-types version accordingly

The new public API that warrants the minor bump:

impl OutPointError {
    /// Attempt to retrieve the out_point from the error.
    pub fn out_point(&self) -> Option<&OutPoint> { ... }
}

All other crates in this release (ckb-constant, ckb-app-config, ckb-network, ckb-tx-pool, ckb-chain, ckb-rpc) have appropriate patch bumps — their changes are internal, value-only constant updates, dependency upgrades with no public API surface changes, or test-only modifications.

Related changes

  • PR to update owner/repo:
  • Need to cherry-pick to the release branch

Check List

Tests

  • No code

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

Co-authored-by: doitian <35768+doitian@users.noreply.github.com>
Copilot AI changed the title [WIP] chore: release new version 1.1.1 and 1.2.1 fix: bump ckb-types to minor version 1.2.0 Mar 20, 2026
Copilot AI requested a review from doitian March 20, 2026 07:04
@doitian doitian closed this Mar 20, 2026
@doitian doitian deleted the copilot/sub-pr-5140 branch March 20, 2026 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants