Skip to content

Next round of breaking changes #378

@joncinque

Description

@joncinque

Problem

For no-std / pinocchio compatibility, we have a set of breaking changes to release.

Proposed Solution

Thankfully, none of these will be as disruptive as the Pubkey v3 / Address v1 publish, since we can use the semver trick for compatibility.

Here is the order of publishing, PRs that need to land, and actions to take:

After this is all done, we make sha256-hasher properly no-std, so that we can land #333.

Here are other publishes that can happen whenever:

  • ✅ frozen-abi-macro: minor (no-std compat)
  • ✅ commitment-config: minor (no-std compat)
  • ✅ epoch-info: minor (no-std compat)
  • ✅ instruction-error: minor (variant deprecation)
  • ✅ short-vec: minor (serde-core compat)
  • ✅ account-info: minor (no-std compat)
  • ✅ sdk-ids: minor (no-std compat)
  • ✅ epoch-rewards-hasher: minor (no-std compat)
  • ✅ program-entrypoint: patch (no msg usage)
  • ✅ sysvar-id: minor (no-std compat)
  • ✅ keypair: minor (address usage)
  • ✅ sysvar: minor (sysvar-get usage)
  • ✅ bincode: minor (serde-core compat)
  • ✅ transaction: patch (serde-core compat)
  • ✅ program-log: major (new crate)
  • ✅ program-log-macro: major (new crate)
  • account-view: major (new crate)
  • ✅ program-memory: minor (upstream compat)

cc @febo @rustopian please check my work!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions