Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 30, 2026

πŸ€– New release

  • canhttp: 0.4.0 -> 0.5.0 (βœ“ API compatible changes)
  • ic-canister-runtime: 0.1.1 -> 0.1.2 (βœ“ API compatible changes)
  • ic-pocket-canister-runtime: 0.2.0 -> 0.3.0 (⚠ API breaking changes)
  • ic-agent-canister-runtime: 0.1.1 -> 0.1.2 (βœ“ API compatible changes)
Changelog

canhttp

0.5.0 - 2026-01-30

Added

  • Add support for batched JSON-RPC requests (#65)
  • Add replicated request extension (#70)

Changed

  • Update dependencies (#72)

ic-canister-runtime

0.1.2 - 2026-01-30

Changed

  • Update dependencies (#72)

ic-pocket-canister-runtime

0.3.0 - 2026-01-30

Changed

  • Breaking: Bump pocket-ic to v12.0.0 (#72)

ic-agent-canister-runtime

0.1.2 - 2026-01-30

Changed

  • Update dependencies (#72)


This PR was generated with release-plz.

@github-actions github-actions bot force-pushed the release-plz-2026-01-30T12-37-30Z branch from 065bd0a to 22cf222 Compare January 30, 2026 13:26
@lpahlavi lpahlavi requested a review from gregorydemay January 30, 2026 14:05
@lpahlavi lpahlavi marked this pull request as ready for review January 30, 2026 14:05
@lpahlavi lpahlavi requested a review from a team as a code owner January 30, 2026 14:05
Copy link
Contributor

@gregorydemay gregorydemay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for creating the release, a minor comment about the verisoning of ic-agent-canister-runtime

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.1.2] - 2026-01-30
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why increasing the patch number? AFAIK this is not a bug fix release so I would go with 0.2.0.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I generally try to avoid bumping the major version for such a small change (just dependency updates here) since this breaks Cargo compatibility. From the docs:

This guide uses the terms β€œmajor” and β€œminor” assuming this relates to a β€œ1.0.0” release or later. Initial development releases starting with β€œ0.y.z” can treat changes in β€œy” as a major release, and β€œz” as a minor release. β€œ0.0.z” releases are always major changes. This is because Cargo uses the convention that only changes in the left-most non-zero component are considered incompatible.

According to semver.org though:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

I guess the right thing to do would be to just bump to v1.0.0 here sooner rather than later... WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, thanks for the explanation! Let's follow the more specific guidelines from Cargo then. I think we should bump everything to v1 once we have JSON-RPC batch used in the EVM RPC canister, WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

@lpahlavi lpahlavi requested a review from gregorydemay February 2, 2026 09:47
@lpahlavi lpahlavi merged commit f45b95c into main Feb 2, 2026
11 checks passed
@lpahlavi lpahlavi deleted the release-plz-2026-01-30T12-37-30Z branch February 2, 2026 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants