Closed guidanoli closed 1 year ago
Latest commit: 3b2f201e9cbeb2240d9171957bcffe176403c466
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
We want to use
changesets
for managing releases, but if@cartesi/rollups
is contained inside a yarn workspace, then the tag thatchangesets
would create would be like@cartesi/rollups@1.2.0
, while we want it to bev1.2.0
. In order to do that, we need to make@cartesi/rollups
no longer part of a yarn workspace, but a package of its own. So, this is the first change.Remove yarn workspace:
check-code-format.yml
to runyarn
insideonchain/rollups
.changeset
toonchain/rollups
onchain/.gitignore
toonchain/rollups/.gitignore
../node_modules
insideonchain/rollups
Taking advantage of this massive change, I also took the freedom to...
yarn
to its latest versioncog.toml
file (and create it only in the CI)build.yml
totest.yml
A second change was the removal of
publish.yml
and addition ofrelease.yml
. Whilepublish.yml
runsyarn npm
directly,release.yml
useschangesets/action
. This command does two things:package.json
andCHANGELOG.md
@cartesi/rollups
) and to GitHub (tag and release)Finally, I needed to move the
CHANGELOG.md
from the repository root toonchain/rollups
, because thechangesets
action expects this file to be in the package root directory. Later, whenrollups-arbitration
gets merged intorollups
, we'll move everything insiderollups
to the repository root, soCHANGELOG.md
will come back to the repository root. Also, I filtered the entries fromCHANGELOG.md
that were not related to@cartesi/rollups
(but were related to the node, for example), and formatted it likechangesets
does it.