🙅🏻‍♂️ Hide instantiator behind feature flag

[JuaniRios]

What?

When on-chain-release-build feature is used, don't compile the instantiator

Why?

Makes the runtime smaller

Testing

• Successfully ran pallet tests, integration tests, benchmark tests, dry-run-benches, and srtool wasm

[JuaniRios]

• 🙅🏻‍♂️ Hide instantiator behind feature flag #389 : 2 dependent PRs (#390 , #391 ) 👈
• ✍🏻 Fix docs #386 : 1 other dependent PR (#387 )
• 🔖 Runtime Upgrade #383
• 💻 Runtime Benchmarks #384
• 🙅🏻‍♂️ Disallow 0CT participation #385
• 🔧 Fix penpal #388
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JuaniRios and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Auto-assign PRs to author" took an action on this PR • (09/03/24)

1 assignee was added to this PR based on Juan Ignacio Rios's automation.

[lrazovic]

Technically, it makes sense to exclude the instantiator from the production build, but this actually increases the runtime size, potentially defeating the purpose of the PR. (You can check in the screenshot the difference in size between this PR, and the previous one in the stack)

While running a few tests with cargo tree, I also noticed that the polimec-common-test-utils crate is also being included in the runtime, which it shouldn't be. We likely need to find a way to exclude that crate from the runtime as well.

[JuaniRios]

Merge activity

• Sep 10, 4:36 AM EDT: @JuaniRios started a stack merge that includes this pull request via Graphite.
• Sep 10, 4:39 AM EDT: Graphite rebased this pull request as part of a merge.
• Sep 10, 4:40 AM EDT: @JuaniRios merged this pull request with Graphite.