test/src/abstract/DecimalFloatDeployChain.t.sol says:
This repo has cut no release under the frozen-record model yet, so
releasedSuites() is empty and the inherited test has no subject and forks
nothing. It gains one the moment the first src/generated/<tag>/ lands.
That is false on main. src/generated/0_1_1/{DecimalFloat,LogTables}.sol are
frozen, LibDecimalFloatReleased declares decimal-float@0_1_1 and
LibLogTablesReleased declares log-tables@0_1_1, so releasedSuites() is
non-empty and the inherited test has a subject and forks every supported
network. A reader is told the test is inert when it is the opposite.
Delete rather than correct, per the ruling on rainlanguage/rain.deploy#153:
naming 0_1_1 re-arms the same trap, because the next release falsifies it again
and nothing expires a comment. The sibling sentence distinguishing this test
from LibDecimalFloatDeployProdTest (CURRENT pins vs a deployment that already
happened) is durable and stays.
Item 2 of rainlanguage/rain.deploy#153, filed here because the file is in this
repo.
test/src/abstract/DecimalFloatDeployChain.t.solsays:That is false on main.
src/generated/0_1_1/{DecimalFloat,LogTables}.solarefrozen,
LibDecimalFloatReleaseddeclaresdecimal-float@0_1_1andLibLogTablesReleaseddeclareslog-tables@0_1_1, soreleasedSuites()isnon-empty and the inherited test has a subject and forks every supported
network. A reader is told the test is inert when it is the opposite.
Delete rather than correct, per the ruling on rainlanguage/rain.deploy#153:
naming 0_1_1 re-arms the same trap, because the next release falsifies it again
and nothing expires a comment. The sibling sentence distinguishing this test
from
LibDecimalFloatDeployProdTest(CURRENT pins vs a deployment that alreadyhappened) is durable and stays.
Item 2 of rainlanguage/rain.deploy#153, filed here because the file is in this
repo.