mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
90547e6ab4
In light of #6127, I kept wondering why rebuilding 1.1.1 would fail. The problem addressed by #6127 is that we tried to rebuild it, which we shouldn't, but the reason I noticed it is because the build failed, and there is no good reason for the 1.1.1 docs to not build anymore. Looking at the logs confused me even more as it failed with (elided): ``` docs/source/support/new-assistant.rst: WARNING: document isn't included in any toctree ``` and that change happened _after_ 1.1.1. So I went back to the code, and discovered I somehow had gotten confused as I changed the approach mid-way through editing the file. If we're overwriting the `release-notes.html` file post-build, which we are now doing (and is the reason for ignoring it when checking checksums), then we should not be touching the `release-notes.rst` file pre-build. CHANGELOG_BEGIN CHANGELOG_END |
||
|---|---|---|
| .. | ||
| azure-cleanup | ||
| cron | ||
| docker/daml-sdk | ||
| patch_bazel_windows | ||
| build-unix.yml | ||
| build-windows.yml | ||
| check-changelog.sh | ||
| compatibility_ts_libs.yml | ||
| compatibility-windows.yml | ||
| compatibility.yml | ||
| configure-bazel.sh | ||
| dev-env-install.sh | ||
| dev-env-push.py | ||
| postgresql.conf | ||
| report-end.yml | ||
| report-start.yml | ||
| slack_user_ids | ||
| tell-slack-failed.yml | ||
| windows-diagnostics.ps1 | ||