Repository navigation
release: rain-factory-deploy 0.1.13 - #53
Merged
Merged
Conversation
0.1.13 carries no source change over 0.1.12. The record freezes the same candidate, so it names the factory already on chain at 0x12E87F6e74195ce93c11948e22BECcf63548Ac40, deployed on all nine networks and verified. 0.1.12 could not publish: the publish job runs `forge script script/Build.sol` first, and rain-deploy 0.1.15's `run()` refused this repo for want of a build hook. That is fixed on main now, but the tag was spent, so the retry is a version. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
0.1.13 carries no source change over 0.1.12. The record freezes the same candidate, so it names the factory already on chain at
0x12E87F6e74195ce93c11948e22BECcf63548Ac40— deployed on all nine networks and verified.Why a third version
sol-v0.1.11NotDeployedOnNetwork("arbitrum", "clone-factory@0_1_11", 0x12E87F6e…). The address moved withrain-factory0.1.30 and had not been broadcast yet.sol-v0.1.12vm.exists: the path script/build.sh is not allowed. rain-deploy 0.1.15'srun()refuses a repo with no build hook.Both causes are now fixed on
main: the deploy landed (run), verification succeeded (run), and #52 adopted the config staging. A tag is the only release trigger and a pushed tag is not re-pushed, so each retry is a version.QA
cutRelease(). What discriminates it is the pair of checks that failed on the previous two tags and pass here:forge script script/Build.solexits 0 (it exited 1 at 0.1.12), andeth_getCodeat0x12E87F6e…returns code on arbitrum, base, base_sepolia, ethereum, flare, hyperevm, robinhood, bsc and polygon — read directly, not from a job log.release-guardfor what the tagged commit must carry, the published package'srun()for what the script demands, and on-chain state for whether the record can publish. None of the three derived from this repo's source.src/generated/0_1_13/frozen, released-suites lib regenerated, config regeneration idempotent after the freeze, and the address it names is live and verified. Deliberately not done — re-pushing either spent tag, and collapsing the three identical records, which the append-only rule forbids.🤖 Generated with Claude Code