SWC-6173

[nickgros]

Update npm publish workflow to manually trigger releases.

This would no longer require code changes to publish new versions of packages, and would also simplify releasing 'patch' versions of packages that do not include all the latest changes.

[Copilot]

Pull Request Overview

This PR transitions from automated npm publishing based on version changes in the main branch to a manual workflow dispatch system. The change allows for more controlled releases by requiring explicit inputs for package name, version, and git reference.

• Replaces automatic version-based publishing with manual workflow triggers
• Resets all package versions to 0.0.0 as a baseline for the new release process
• Updates documentation to reflect the new manual release workflow

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

File	Description
packages/*/package.json	Reset package versions to 0.0.0 for new manual release process
.github/workflows/npmpublish.yml	Removed old automated workflow that triggered on version changes
.github/workflows/npm-publish.yml	Added new manual workflow with dispatch inputs for controlled releases
README.md	Updated documentation to describe new manual release process

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[nickgros]

Set all packages to v0.0.0 since the version is set in the workflow. The engineer releasing the new version should reference NPM or the repository tags to identify the previous release version.

[jay-hodgson]

Is there a relatively easy way to automatically generate the SRC release notes and set as the latest release?

[nickgros]

@jay-hodgson Not sure if we want to automate that, the generated release notes are not scoped to each package (includes all changes in the repo) so that should probably remain a manual process (e.g. if release a new version of markdown-it-synapse, we don't want the release to include all repo changes since the previous release)

[nickgros]

Actually, I am not sure how this will work with the workspace:* identifiers in our package.json. This could break internal transitive dependencies