[Cairo] Add ERC1155Supply to 4.0.0-alpha.0

[ericnordelo]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[ericglau]

This says 3.1.0 but packages/core/cairo_alpha/package.json says 4.0.0-alpha.0 (the same occurs in the other PRs)

[ericnordelo]

Oh, I updated because I remembered you mentioned at some point that wizard releases and the version of the contracts library were not pegged, and also the rest of this file follow the format of not using alphas. We still need alpha in the package.json version because that is used in the alpha switch in the UI, right?

[ericglau]

Right, the versions don't need to be pegged, but using Contracts for Cairo v4 is a breaking change.

We can just leave this line as

Suggested change

	## 3.1.0 (Unreleased)
	## Unreleased

---

More detailed explanation (we should document this process):

The alpha switch label uses contractsVersionTag from packages/core/cairo_alpha/src/utils/version.ts.

All packages use changesets, except for cairo_alpha (which is excluded from the NPM release process, so we manually keep track of changes in its CHANGELOG.md. Those entries need to be manually moved into a changeset when we eventually promote it from alpha to stable for release).

When we merge/promote alpha to stable, we'll need to do the following in the resulting PR:

1. Move the contents of ## Unreleased section to a changeset (new .md file under .changeset), targeting a major version bump of @openzeppelin/wizard-cairo
2. Ensure the version of packages/core/cairo/package.json is NOT bumped manually (e.g. it must remain 3.x when we want to release 4.0.0)
3. The version packages workflow (prior to release) will: consume the changeset, move it to packages/core/cairo/CHANGELOG.md, and update the version in packages/core/cairo/package.json