You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release procedures in the Reame.md: https://github.com/finos/FDC3/blob/main/README.md#releasing-fdc3-to-npm-for-maintainers require manual intervention by FINOS when issuing a prerelease, due to the fact that they tag whatever version is pushed as latest, which then needs to be manually reset via an account with rights on NPM (not shared with maintainers).
To simplify the issuing prereleases, we should:
Check that all package version numbers are in sync (fail otherwise)
Process the (common to all packages) version number to extract/detect prerelease details (2.2.0**-beta.1**).
If a prerelease tag is found, prevent tagging as latest by specifying a different tag. This could either be the prerelease tag itself (e.g. beta) or simply prerelease
The text was updated successfully, but these errors were encountered:
The release procedures in the Reame.md: https://github.com/finos/FDC3/blob/main/README.md#releasing-fdc3-to-npm-for-maintainers require manual intervention by FINOS when issuing a prerelease, due to the fact that they tag whatever version is pushed as
latest
, which then needs to be manually reset via an account with rights on NPM (not shared with maintainers).To simplify the issuing prereleases, we should:
beta
) or simplyprerelease
The text was updated successfully, but these errors were encountered: