v1-beta.1 release

[austinletson]

• Create a release/v1-beta.1 branch off of main for the release candidate.
• Testing
  • Run functional_tests.yml workflow on release/v1-beta.1.
  • Test release/v1-beta on existing test projects (Given that the automated functional tests cover much of the original manual functional test suite, this is more of a sanity check).
• Create a release of release/v1-beta.1 with a v1-beta.1 tag.
  • Copy the release notes from the ## Unreleased section of CHANGELOG.md.
• Git tag manipulation.
  • Create a v1-beta.0 tag to point to v1-beta to preserve a tag to the last release.
  • Move the v1-beta tag to point to v1-beta.1.
• Verify action with uses: leanprover/lean-action@v1-beta.
• Create a PR to update README.md and CHANGELOG.md.
• Post in Zulip
• Create an issue to update RELEASING.md with improvements to the release process and add a template for release issues.

[austinletson]

Functional tests for release/v1-beta.1

Automated tests

The functional test suite for lean-action has been automated since the last release. here is a run of the functional_tests.yml workflow targeted at release/v1-beta.1.

Manual tests

As this is the first time using the automated test suite to test a release, I ran a few manual functional tests as a sanity check.

Bare Lean Pacakge

• link to workflow run

Subdirectory Lean Package

- uses: leanprover/lean-action@release/v1-beta.1
  with:
    test: false
    lake-package-directory: './subdirectory'

• link to workflow run

[austinletson]

Created post on Zulip and #68 to track improvements to the release process.