Add Changesets support #84
Conversation
ynotdraw
force-pushed
the
changesets-support
branch
from
122c2d0
to
7acf12c
Compare
🦋 Changeset detectedLatest commit: 5b49970 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
ynotdraw
force-pushed
the
changesets-support
branch
from
7acf12c
to
632ffa4
Compare
ynotdraw
requested review from
vitch,
camskene,
nicolechung,
simonihmig,
danwenzel and
joelamb
| @@ -10,11 +10,16 @@ | |||
| "test": "pnpm --filter test-app test", | |||
| "lint": "pnpm --filter '*' lint", | |||
| "lint:fix": "pnpm --filter '*' lint:fix", | |||
| "ci:update": "npx ember-ci-update" | |||
| "ci:update": "npx ember-ci-update", | |||
There was a problem hiding this comment.
Unrelated to this PR, what what is this???
There was a problem hiding this comment.
One of my attempts to make managing the big ci.yml in .github/workflows/ easier.
One thng it still does nicely ds keep your ember-try config in sync with CI.
The main thing is that when this was made, each job required 10 or so lines of setup, and it was rually overwhelming
I've since abandoned it as i've learned about:
- in-repo custom actions
- actual custom actions published to the market place.
I now use wyvox/action@v1 in new workflows, and NullVoxPopuli/action-setup-pnpm@v2 where i want more control back.
This has the desired effect of making the workflow files way less overwhelming while also providing something that ds easier to maintain .
For wyvox/action, i've been meaning to add the turbo server to it, but haven't gotten around to it
There was a problem hiding this comment.
Starting with: wyvox/action#1
it now supports turborepo.
Example workflow: https://github.com/NullVoxPopuli/v2-addon-project-template/blob/main/.github/workflows/ci.yml
ynotdraw
force-pushed
the
changesets-support
branch
from
02ef4bc
to
5b49970
Compare
Description
This PR moves to using Changesets over semantic-release. The reason here is so that the repos we work in most frequently use the same tooling so that we have similar DX across all projects. The following projects use changesets:
ember-toucan-coreember-headless-formember-headless-tabletailwind-toucan-baseember-toucan-stylesThis should roughly match this PR.