diff --git a/RELEASE.adoc b/RELEASE.adoc index 45ab002a325..616978c8211 100644 --- a/RELEASE.adoc +++ b/RELEASE.adoc @@ -87,28 +87,23 @@ For instance, if `plutus-ledger-api` is the only package changed, there is no ne Another example is if a security audit is done on `rc1`, and the changes in `rc2` do not modify the audited code, then the audit does not need to be re-done. - If another CHaP PR gets merged before yours it will invalidate the timestamps and you won't be able to merge: see the https://github.com/IntersectMBO/cardano-haskell-packages/blob/main/README.md[CHaP README file], in particular https://github.com/IntersectMBO/cardano-haskell-packages/blob/main/README.md#monotonically-increasing-timestamps[this section]. Read https://github.com/IntersectMBO/cardano-haskell-packages/blob/main/README.md#dealing-with-timestamp-conflicts[this section] for advice on how to deal with this problem. -8. Once the CHaP PR has been merged, make a PR to update the version used in `cardano-ledger`. Example: https://github.com/IntersectMBO/cardano-ledger/pull/3563. -- Update the version bounds in cabal files. -- Update the CHaP index state in `cabal.project`. -- Update the CHaP flake input with `nix flake update CHaP`. If you get "error: cannot find flake 'flake:CHaP' in the flake registries" your nix installation probably needs to be updated. - -9. Make a PR to update the version used in `plutus-tx-template` +8. Make a PR to update the version used in `plutus-tx-template` - Navigate to the https://github.com/IntersectMBO/plutus-tx-template/actions/workflows/bump-plutus-version.yml[Bump Plutus Version Action] on GitHub - Click the `Run workflow` button on the right, enter the new release version and confirm - This will automatically open a PR in `plutus-tx-template` with auto-merge enabled - Ensure that CI is green and the PR gets merged -10. Publish the updated Metatheory site +9. Publish the updated Metatheory site - Navigate to the https://github.com/IntersectMBO/plutus/actions/workflows/metatheory-site.yml[Metatheory Site Action] on GitHub -- Click the `Run workflow` button on the right, enter the new release version and confirm +- Click the `Run workflow` button on the right, enter the new release version 2 times, leave the checkbox Enabled, and confirm - Ensure that the action completes successfully -11. Publish the updated Haddock site +10. Publish the updated Haddock site - Navigate to the https://github.com/IntersectMBO/plutus/actions/workflows/haddock-site.yml[Haddock Site Action] on GitHub - Click the `Run workflow` button on the right, enter the new release version 2 times, leave the checkbox Enabled, and confirm - Ensure that the action completes successfully -12. Delete unused branches and tags +11. Delete unused branches and tags - If it was created, delete the `release/*` branch locally and on GitHub - If they were created, delete any release candidate `-rc*` tags locally and on GitHub