Skip to content

Commit ee4aa34

Browse files
committed
fix(release): update Cargo.lock for demo crate
Because we now run the tests before releasing, cargo may bump the version in demo_seccomp and that would result in a `dirty` version passed around. Fix it properly by also running `cargo check` on demo_seccomp. Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
1 parent d4faa70 commit ee4aa34

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

tools/release-prepare.sh

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,16 +70,24 @@ done
7070
# `Cargo.lock`.
7171
say "Updating lockfile..."
7272
cargo check
73+
CHANGED=(Cargo.lock)
74+
75+
cd tests/integration_tests/security/demo_seccomp
76+
cargo check
77+
cd -
78+
CHANGED+=(tests/integration_tests/security/demo_seccomp/Cargo.lock)
7379

7480
# Update credits.
7581
say "Updating credits..."
7682
$FC_TOOLS_DIR/update-credits.sh
83+
CHANGED+=(CREDITS.md)
7784

7885
# Update changelog.
7986
say "Updating changelog..."
8087
sed -i "s/\[Unreleased\]/\[$version\]/g" "$FC_ROOT_DIR/CHANGELOG.md"
88+
CHANGED+=(CHANGELOG.md)
8189

82-
git add "${files_to_change[@]}" Cargo.lock CREDITS.md CHANGELOG.md
90+
git add "${files_to_change[@]}" "${CHANGED[@]}"
8391
git commit -s -m "Releasing v$version"
8492

8593

0 commit comments

Comments
 (0)