Delete vestigial last_run.uuid file #2236
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file gets written with a random UUID every time you download the schema. The line that writes it was added in #119 along with a special `cargo:rerun-if-changed` command to control if Cargo is rerun. However, that check was removed in #1166. (And then this entire update procedure was moved from `build.rs` to an explicitly-run `xtask` command in #1424.) So it seems like this file is completely vestigial at this point and doesn't need to be updated when you update the schema.
✅ Docs Preview ReadyNo new or changed pages found. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This file gets written with a random UUID every time you download the schema. The line that writes it was added in #119 along with a special
cargo:rerun-if-changedcommand to control if Cargo is rerun. However, that check was removed in #1166. (And then this entire update procedure was moved frombuild.rsto an explicitly-runxtaskcommand in #1424.)So it seems like this file is completely vestigial at this point and doesn't need to be updated when you update the schema.