Skip to content

Simplify publication of prerelease packages to NPM #1528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kriswest opened this issue Feb 28, 2025 · 0 comments
Open

Simplify publication of prerelease packages to NPM #1528

kriswest opened this issue Feb 28, 2025 · 0 comments
Labels
help wanted Extra attention is needed project infrastructure

Comments

@kriswest
Copy link
Contributor

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed project infrastructure
Projects
None yet
Development

No branches or pull requests

1 participant