read what the binary says about itself: names, signatures, prototypes; gen v2
This commit is contained in:
parent
54ef572202
commit
c458b4cb50
34 changed files with 58363 additions and 192 deletions
|
|
@ -86,9 +86,6 @@ jobs:
|
|||
|
||||
- name: Produce — validate the contribution live (no model fold; the build is unchanged)
|
||||
run: |
|
||||
# The model already contains this build (derive folded it), and the forward-only guard needs the
|
||||
# target to sort strictly after the model's latest. "<buildid>-<patch>" does: it shares the buildid
|
||||
# prefix and is longer, and the next update's buildid still sorts above it.
|
||||
ln -sfn "$GAME_DIR" "work/$BUILDID-$PATCH"
|
||||
./target/release/source2rosetta --game "$GAME" produce \
|
||||
--seed "seed-$GAME.patched.json" \
|
||||
|
|
@ -100,9 +97,6 @@ jobs:
|
|||
cp "seed-$GAME.patched.json" "dist/seed-$GAME.json"
|
||||
|
||||
- name: Drop the re-folded model, compress the seed
|
||||
# A contribution does not change the binary, so the sidecar fold just re-folds a build the model
|
||||
# already has. Publishing that would append a duplicate row and grow the model on every PR — so the
|
||||
# model asset is left alone and `<game>-latest` keeps the one the last derive published.
|
||||
run: |
|
||||
rm -f "dist/model-$GAME.json"
|
||||
gzip -6 "dist/seed-$GAME.json"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue