Repository navigation
ci: publish with mops 3.5.1, which benchmarks on moc 2 - #30
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Kamirus
added a commit
that referenced
this pull request
Oct 19, 2026
How releases reach Mops, and what they depend on, now lives in `RELEASING.md` instead of only in PR descriptions. It covers the release steps, publishing an existing tag again, the `MOPS_IDENTITY_PEM` secret and the GitHub App the workflows need, and the mops version pin that broke the first 0.2.2 publish. The repo had no `AGENTS.md`. The new one follows motoko-core's: setup, test, benchmark, and format commands, the layout, and a link to `RELEASING.md`. `CLAUDE.md` imports it. The `Releasing` section of `README.md` now links to `RELEASING.md` for the details. Follow-up to [#29](#29) and [#30](#30). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.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.
The first
Publish on Mopsrun forv0.2.2(run) failed while benchmarking:mops publishruns the benchmarks itself. Up to 3.4.2 it hard-coded legacy-persistence flags, andmoc2.0.0 doesn't accept them. The regularmops benchin CI was already fixed, which is why tests passed. mops 3.5.0 makespublishuse the samemocflags asbench, so the workflow now pins 3.5.1. With 3.5.1,mops publish --dry-run --no-teston this tree passes locally.mops publishalso getsGITHUB_TOKEN. Since 3.5.0, mops uses it to read release notes, instead of making anonymous requests that a shared runner can find already rate-limited.Follow-up to #29. After merge,
Publish on Mopsgets dispatched again with tagv0.2.2.🤖 Generated with Claude Code