@@ -2,27 +2,27 @@ Checklist for Tagging a New Release
2
2
----------------------------------------------------------
3
3
- Update the version = "x.y.z" line near the top of Project.toml
4
4
to be the new version number and commit this change
5
- - On the Github website for ITensors.jl, click on Code tab,
6
- then the link to the individual commits (showing total
5
+ - On the Github website for ITensors.jl, click on Code tab,
6
+ then the link to the individual commits (showing total
7
7
number of commits) then click on a commit occurring on
8
8
or after the change to Project.toml
9
9
- In the comments under this commit, add the comment:
10
10
@JuliaRegistrator register
11
11
- Wait an hour or so for the JuliaRegistrator bot to
12
- update the official Julia registry
12
+ update the official Julia registry
13
13
- The TagBot bot should also create a new tag and version on Github
14
14
automatically (if you see a notice about "Trigger TagBot Issue"
15
- it does not mean that TagBot isn't working or has an issue, it
15
+ it does not mean that TagBot isn't working or has an issue, it
16
16
is just literally a Github issue used to trigger TagBot to run)
17
- - TagBot helpfully explains the differences from the previous
17
+ - TagBot helpfully explains the differences from the previous
18
18
versions in the Github version entry. This can be useful for
19
19
updating the NEWS.md file.
20
20
21
21
Checklist for Updating the Version of Documenter.jl Used
22
22
----------------------------------------------------------
23
23
- Edit the docs/Project.toml file, changing only the version
24
24
number for Documenter (under the [compat] section).
25
- - Create a new PR to confirm that the docs build correctly
25
+ - Create a new PR to confirm that the docs build correctly
26
26
with the new version.
27
27
28
28
Checklist for Updating the Benchmark CI for New Dependencies
0 commit comments