Plutus Release 1.46.0.0

[Unisay]

Plutus Release 1.46.0.0

[zliu41]

I'd prefer not releasing from a commit that is neither on master nor on a release branch. Let's discuss it before proceeding.

[Unisay]

I'd prefer not releasing from a commit that is neither on master nor on a release branch. Let's discuss it before proceeding.

The commit we're releasing is on the release branch though IntersectMBO/plutus@66029b4

[zliu41]

Right, but there are a few issues:

• After merging the Plutus PR, branch release/1.46.0.0 will be deleted, and the commit will become a dangling commit - subject to GC.
• I think a more common practice is to name the release branch release/1.46, and release all minor versions (1.46.1, 1.46.2 etc.) from that branch. This is what we used to do. Let's discuss which option is better.

[Unisay]

• After merging the Plutus PR, branch release/1.46.0.0 will be deleted, and the commit will become a dangling commit - subject to GC.

Point taken - will make sure that release PR in the plutus repository merges that commit to master without rewriting git history (e.g. no git squash).

[Unisay]

Merging the PR despite failing hydra checks: github actions pass but Hydra doesn't take into account latest revisions of the random package properly.