enclawed-release-maintainer

To manage npm publish and macOS release workflows together, you need to orchestrate version alignment, changelog generation, and artifact validation across both targets before creating tags. This ensures consistent releases across platforms without breaking existing installs.

Preparing a beta release with changelog notes requires aligning version fields across npm, macOS, docs, and tags for the beta channel. You must run preflight build checks, validate artifacts, and coordinate GitHub release creation before publishing.

Yes, GitHub Actions can coordinate Sparkle feed updates and npm dist-tag handling by orchestrating the release process sequentially. The workflow must enforce strict publish guardrails, verify build artifacts, and update the macOS appcast only after validation passes.

Validation steps before creating a stable release tag require running build, install smoke, and release checks to verify artifacts. These preflight checks ensure npm and macOS packages pass approved publish workflows and artifact verification before any tag or publication proceeds.

Version alignment for correction releases does need separate changelog notes to document the specific fixes applied. The process keeps npm, mobile, macOS, docs, and tag naming consistent while applying the same preflight validation as standard releases.

Release guardrails matter when publishing macOS and npm artifacts because they enforce preflight checks and artifact verification before any tag creation or publish action proceeds. Strict adherence prevents broken installs and ensures only validated builds reach the release channel.