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
versions numbers are un-sync everywhere, since refmt --version often lies (is going away on Fix version on refmt #2701), bs-platform shipping with a packaged refmt for 3.6.2 makes stuff more confusing as well.
The only way to use a "nightly" release of Reason, you need to pin which is a sub-par experience when Reason is as a transitive dependency.
We manually check if an entry to CHANGELOG is added (instead of a tool checking it for us)
Most scripts (opam-release, release-check and test-with-version) are probably unused, wrong and rely on personal GH tokens.
Opening this issue as gathering information to fix it and if it's worth the effort. There have been a few issues in the past: #2418#2461#2453
Proposed solution
GH actions should handle all release processes, publish to npm and open the PR to opam-repository.
version=X.X.X make pre_release
This should do everything for you:
Update accordingly version everywhere: esy.json, reason.json, rtop.json and dune-project
Create a git tag
Create a commit message
Push to origin with tags
The CI should handle:
Running node ./scripts/esy-prepublish.js
cd _release/XXX/package/
npm publish --access=public
Running opam-publish
Notes: We can't use %%VERSION%% and dune subts in esy.json files since esy doesn't recognise %%VERSION%% as a valid one. We would need to do something less fancy:
Currently, the release process has a few issues, the root is that it is done manually, so some steps might be skipped which results in problems:
refmt --version
often lies (is going away on Fix version on refmt #2701), bs-platform shipping with a packaged refmt for 3.6.2 makes stuff more confusing as well.Opening this issue as gathering information to fix it and if it's worth the effort. There have been a few issues in the past: #2418 #2461 #2453
Proposed solution
GH actions should handle all release processes, publish to npm and open the PR to opam-repository.
This should do everything for you:
The CI should handle:
Running node ./scripts/esy-prepublish.js
cd _release/XXX/package/
npm publish --access=public
Running opam-publish
Notes: We can't use %%VERSION%% and dune subts in esy.json files since esy doesn't recognise %%VERSION%% as a valid one. We would need to do something less fancy:
The text was updated successfully, but these errors were encountered: