Repository navigation
chore: release v0.8.0 - #30
Merged
Merged
Conversation
Everything since v0.7.0 is the ceremony profile generator (#29): `profiles.json` becomes the one place the profile values live, and Solidity, Rust and TypeScript are generated from it, following `handles.json`. The Solidity constants are unchanged -- the diff against the previous `CeremonyProfile.sol` is additions only, and its 439 tests pass untouched. `libid-profiles` is a new published crate, so this release puts a fourth manifest under the single-version invariant and a third crate on crates.io. Assisted-by: Claude Opus 5 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
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.
Sets every manifest to
0.8.0: the three crates and the npm package, plus the lockfile entry.Minor rather than patch — this release adds a published crate (
libid-profiles) and new public constants — and nothing breaking: the Solidity constants generated by #29 are byte-for-byte whatCeremonyProfile.solalready held, and the verifiers behave identically.Everything since v0.7.0 is #29.
Checked before opening
verify-tag.sh v0.8.0— three crates and npm all read 0.8.0, and match the tagregen-ceremony-profiles.py --checkandregen-identity-handles.py --check— generated tables current, which the release now waits on:publish-cratesgainedgenerated-tablesin itsneedslibid-profiles0.8.0 is unclaimed on crates.io (it has no published version at all yet)After merge
gh release create v0.8.0publishes to crates.io and npm. That step is irreversible on both registries, so I have not run it — say the word.