You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto merge of #115898 - onur-ozkan:config-change-tracking, r=Mark-Simulacrum
bootstrap major change detection implementation
The use of `changelog-seen` and `bootstrap/CHANGELOG.md` has not been functional in any way for many years. We often do major/breaking changes but never update the changelog file or the `changelog-seen`. This is an alternative method for tracking major or breaking changes and informing developers when such changes occur.
Example output when bootstrap detects a major change:

msg.push_str("To see more detail about these changes, visit the following PRs:\n");
121
+
for link in change_links {
122
+
msg.push_str(&format!(" - {link}\n"));
123
+
}
124
+
}
125
+
msg.push_str("WARNING: there have been changes to x.py since you last updated.\n");
126
+
format!("update `config.toml` to use `change-id = {latest_config_id}` instead")
111
127
}else{
112
128
returnNone;
113
129
}
114
130
}else{
115
-
msg.push_str("warning: x.py has made several changes recently you may want to look at\n");
116
-
format!("add `changelog-seen = {VERSION}` at the top of `config.toml`")
131
+
msg.push_str("WARNING: The `change-id` is missing in the `config.toml`. This means that you will not be able to track the major changes made to the bootstrap configurations.\n");
132
+
format!("add `change-id = {latest_config_id}` at the top of `config.toml`")
117
133
};
118
134
119
-
msg.push_str("help: consider looking at the changes in `src/bootstrap/CHANGELOG.md`\n");
0 commit comments