Pulsar Release Workflow

This repository is dedicated to automating the Pulsar Regular Release process.

Within this repository is an action that must be triggered to begin the regular release cycle.

The code in this repository is broken up into distinct steps to help communicate and separate the concerns of what is happening.

Usage

Using this automation should be fairly simple. Further documentation of this should be created in pulsar-edit/.github, but until then, the following steps must be taken for a successful release.

1. Ensure all PRs are merged into master on Pulsar.
2. Create and merge to master a full and complete CHANGELOG.md.
3. Manually tigger the "Automated Regular Release (Full)" regular-release.yaml step.
4. Once completed ensure the draft release on GitHub looks correct.
5. Merge the version update PR to master on Pulsar.
6. Update the release notes and post the release.
7. Manually trigger the "Followup Steps to Regular Release" release-followups.yml step.
8. Review and merge the PRs created for:

• pulsar-edit/documentation
• pulsar-edit/pulsar-chocolatey
• pulsar-edit/pulsar-edit.github.io (This one will require the blog post to be added manually)

9. Manually post the new release news to all social channels.

Steps to Achieve Complete Automation:

• Create branch for new version
• Bump new Version
• Tag new Version
• Create PR to pulsar with new version
• Download bins from GitHub
• Download bins from CirrusCi
• Generate SHA256SUMs for bins
• Create GitHub Release for new version
• Upload assets to new version
• Cleanup new version branch & PR
• Create Chocolatey Release
• Update download links
• Update website blog
• Update Documentation Website (Needs pulsar-edit/documentation#14 merged before functional)
• Post news to socials:
  • Discord
  • Mastodon
  • Reddit
  • Lemmy