Release 1.0.2 - #5
Merged
Merged
Conversation
…tible), synchronous JS SHA-256 miner, accurate docs
…gation (CI flake)
performance: bounded replay store, synchronous JS SHA-256 miner, accurate cost docs
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.
Version 1.0.1 → 1.0.2 plus the performance changes from #4.
Why this PR contains more than a version bump: #4 was merged while its base was still
refactor/architecture, so its merge commit (cf6e37b— the perf work incl. the e2e flake fix58046a5) landed on that branch, not onmain. This branch is cut from that tip and adds the release commit on top, so merging it brings #4's changes and the 1.0.2 bump intomainin one step.Changes
cardea.php(header +CARDEA_VERSIONdefine — the PHPUnit bootstrap parses this, so no test hard-codes the version)package.json+package-lock.json(both root version fields, same convention as the 1.0.1 release)readme.txtStable tag= 1.0.2 =covering the merged work (REST PoW parity, unified failure messages, difficulty-at-verify, capped self-pruningcardea_usedreplay store, synchronous in-worker SHA-256 miner, WP 7.1set_option()→update_option(),Cardea_Comment_Gate, docs).= 1.0.2 =entry.Content of #4 carried by this branch
assets/js/pow-worker.js— synchronous FIPS 180-4 SHA-256 miner (KATs +node:cryptocross-checks in jest), unbounded counter, nocrypto.subtle(works on plain HTTP)includes/class-cardea-core.php—cardea_usedcapped (1024) self-pruning replay store viaupdate_option()(WP 7.1 removedset_option()— verified on a live WP 7.1 Playground)uninstall.php—delete_option('cardea_used')+ legacy transient sweepincludes/class-cardea-admin.php— difficulty solve-time guidancetests/js/pow-worker.test.js— real-worker suite (16 tests)tests/e2e/pow-comment.spec.js:153— CI flake fix (settle the post-submission redirect before re-navigating)README.md/readme.txt— accurate replay-store/HTTP docsTest evidence
Full suite green on this branch (Docker,
make test+make lint):Post-merge release steps:
make package(freshdist/cardea.zip) →make sync-svn+tags/1.0.2→svn commit -m "1.0.2 - REST PoW parity, bounded replay store, sync JS miner, WP 7.1 set_option() compatibility".