|
13 | 13 | incremented since the last release, so they do not necessarily need |
14 | 14 | to be updated. However, you may want to increment them further |
15 | 15 | depending the types of changes that are in the release. |
| 16 | + |
16 | 17 | 1. Run `Scripts/prepare_release.py $VER prepare --source-branch <this branch>` |
17 | 18 | (`--source-branch` is optional and defaults to 'master') |
18 | 19 | from the root of the repository. The script will check that the repository is in a good |
19 | 20 | state, create and check out a new release branch, update |
20 | 21 | `Source/Directory.Build.props` and `RELEASE_NOTES.md`, prepare a release commit, |
21 | 22 | and push it. |
22 | 23 |
|
23 | | -1. Kick off the deep test suite by navigating to |
24 | | - <https://github.com/dafny-lang/dafny/actions/workflows/deep-tests.yml>, |
25 | | - clicking the "Run workflow" dropdown, selecting the newly created branch, and |
26 | | - clicking the "Run workflow" button. The automation for releasing below will |
27 | | - check for a run of this workflow on the exact commit to release. (TODO: |
28 | | - Run this automatically as part of the prepare-release script.) |
29 | | - |
30 | | -1. Once the the tests complete, run `Scripts/prepare_release.py $VER |
| 24 | +1. Run `./Scripts/prepare_release.py $VER |
31 | 25 | release` from the root of the repository. The script will tag the |
32 | | - current commit and push it. (TODO: Merge with the two steps above.) A |
| 26 | + current commit and push it. A |
33 | 27 | GitHub action will automatically run in reaction to the tag being |
34 | | - pushed, which will build the artifacts and reference manual and then |
| 28 | + pushed, which will run the deep integration test suite, |
| 29 | + build the artifacts and reference manual, |
| 30 | + publish artifacts to nuget.org, and then |
35 | 31 | create a draft GitHub release. You can find and watch the progress of |
36 | 32 | this workflow at <https://github.com/dafny-lang/dafny/actions>. |
37 | 33 |
|
|
0 commit comments