Skip to content

fix: scaffold.yml v2 fast-follows for the 1.0 preview - #283

Merged
chadoh merged 1 commit into
mainfrom
fix/scaffold-v2-quick-fixes
Oct 23, 2026
Merged

chadoh merged 1 commit into
mainfrom
fix/scaffold-v2-quick-fixes

Conversation

@zachfedor

Copy link
Copy Markdown
Contributor

Fast-follow fixes for scaffold.yml v2, planned or found during Q3 and proposed for early Q4, ahead of the pre-hackathon release.

  • New projects no longer inherit Scaffold's authors and repository, which cargo_inherit wrote into every contract's Wasm metadata

Pairs with stellar-scaffold/cli#632.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QhmaWLv4yExX8LahP5UtUb

@zachfedor zachfedor added the cross-repo Opt-in to cross-repo testing on matching branch names label Oct 17, 2026
@zachfedor
zachfedor requested a review from chadoh October 17, 2026 16:24
@chadoh

chadoh commented Oct 21, 2026

Copy link
Copy Markdown
Contributor
  • New projects no longer inherit Scaffold's authors and repository, which cargo_inherit wrote into every contract's Wasm metadata

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:

image

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 repository, we should add authors.workspace = true to each contract.

@pselle wdyt?

@pselle

pselle commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

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?

@pselle

pselle commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Something like

[workspace.package]
# authors = ["Your Name <you@example.com>"]
# repository = "https://github.com/you/your-project"

commented so that it doesn't end up published on accident

@pselle

pselle commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

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

@chadoh
chadoh force-pushed the fix/scaffold-v2-quick-fixes branch 2 times, most recently from 2ab9408 to 348cdfd Compare October 22, 2026 15:53
Comment thread Cargo.toml Resolved
Comment thread Cargo.lock Resolved
@chadoh
chadoh marked this pull request as draft October 22, 2026 17:16
chadoh added a commit to stellar-scaffold/cli that referenced this pull request Oct 22, 2026
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.
@chadoh
chadoh force-pushed the fix/scaffold-v2-quick-fixes branch from 152244c to 32c69cd Compare October 22, 2026 20:25
@chadoh
chadoh marked this pull request as ready for review October 22, 2026 20:25
@chadoh chadoh removed the cross-repo Opt-in to cross-repo testing on matching branch names label Oct 22, 2026
@chadoh
chadoh merged commit 6d9890d into main Oct 23, 2026
3 of 5 checks passed
@chadoh
chadoh deleted the fix/scaffold-v2-quick-fixes branch October 23, 2026 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants