Sohrab
Sohrab
@armaniferrante, there is a circular dependency in [`test-anchor-init` test](https://github.com/coral-xyz/anchor/runs/6960769247?check_suite_focus=true). `anchor init` automatically does a `yarn insall` so the npm package has to be published before it can succeed. I thought...
I've got the Anchor book changes I can PR, once we have an npm package published.
I think this may have caused too much friction and now it is way out-of-date too.
This is so close! Anything I can do to help?
I'm guessing this won't be resolved till the next version?
I dunno if this helps anyone but I built the x86_64 binary from 0.25.0 crate and made it available here: https://github.com/labeleven-dev/anchor-binaries/releases/tag/1.0.0 More info in [README.md](https://github.com/labeleven-dev/anchor-binaries/blob/main/README.md)
0.26.0 has been released with the correct binaries now.
Here is the manifest if anyone needs the work-around: ```typescript import { CandyGuardManifest, createSerializerFromBeet, } from "@metaplex-foundation/js"; import { Allocation, allocationBeet, } from "@metaplex-foundation/mpl-candy-guard"; export const allocationGuardManifest: CandyGuardManifest = {...
Lemme see if I can understand what it does. The manifest is easy enough but need to know what it does to write the proper unit tests 😅
I am not sure if there is something still forthcoming but as it stands, I find it a bit jarring when the SDK provides you with a _bag_ of functions...