Repository navigation
fix: scaffold.yml v2 fast-follows for the 1.0 preview - #283
Conversation
This is obviously a problem, but I wonder if it's more of a documentation problem. In our handout for the hackathon, I included this line:
If we get better at reminding people to do this in our docs, I think we might want the opposite of this PR: rather than removing @pselle wdyt? |
|
Edited: (if you got an email, this comment completely changed!) Sorry now I get it -- so that we don't accidentally have a bunch of projects saying The Aha Company etc. But perhaps we should have a fake company there, like ACME Corp? Or comments? Something to it's not us but gives people a placeholder to replace? |
|
Something like commented so that it doesn't end up published on accident |
|
side note: the cargo.lock here seems to have extra noise, might want to check on that if you push to this or replace the PR with another PR |
2ab9408 to
348cdfd
Compare
Fast-follow fixes and improvements for `scaffold.yml` v2 which didn't make the Q3 deadline and were planned/proposed for early Q4, ahead of the hackathon release. - `init` copies `app/.env.example` to `app/.env`; `doctor` checks there too. Fixes #568 - `init` builds with the project's `rust-toolchain.toml`, so the first `npm start` no longer redeploys every contract - `watch` rebuilds on editors that save by renaming over the file - `init` and `doctor` check Docker and the local network for v2 projects with any locally run network. Part of #621 (extensions check still to do), part of #604 - `init` shows its build output with `-v` or `-vv`. Part of #604 - `init` names the network it deploys to and warns that the first local run downloads the quickstart image (stellar-scaffold/ui#216) - Docs revert to recommending `cargo binstall` first and list the remaining prerequisites (C toolchain, Linux system libraries). This is a revert of a revert when we had those lagging binstall release issues. Pairs with stellar-scaffold/ui#283. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01QhmaWLv4yExX8LahP5UtUb --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Co-authored-by: Warp <agent@warp.dev>
The example contracts inherited `authors` and `repository` from the workspace, set to The Aha Company and the Scaffold CLI repo. Their `cargo_inherit` metadata writes those into the Wasm, so contracts built or published from a new project claimed to come from us. Projects now start with these values and also `homepage` set to blank values, and all member contracts set to inherit them, with a comment in the root Cargo.toml telling people to set the values. Corresponding change stellar-scaffold/cli#640 ensures blank `home_domain` and `source_repo` values don't end up in the Wasm.
152244c to
32c69cd
Compare

Fast-follow fixes for
scaffold.ymlv2, planned or found during Q3 and proposed for early Q4, ahead of the pre-hackathon release.authorsandrepository, whichcargo_inheritwrote into every contract's Wasm metadataPairs with stellar-scaffold/cli#632.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QhmaWLv4yExX8LahP5UtUb