chore: monorepo #1679
chore: monorepo #1679
Conversation
P0lip
force-pushed
the
chore/monorepo
branch
6 times, most recently
from
3cd1149 to
616e871
Compare
|
🎉 This PR is included in version @stoplight/spectral-cli-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-core-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-rulesets-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-runtime-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-functions-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-formats-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-parsers-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @stoplight/spectral-ref-resolver-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Closes #1614
Checklist
Does this PR introduce a breaking change?
Additional context
I suggest to review the PR commit by commit.
There's a bit of noise that's a result of src -> packages move, but this took place in the first commit.
I introduced 2 breaking changes I was planning to do it anyway.
Note on the release - it's still not quite set up yet.
I'm planning to add a cron job to CircleCI to release some packages with a certain cadence.
However, to accomplish that, I'll need to integrate Lerna with semantic-versioning to make sure the process is automated and we don't need to do anything manually.
Ideally, rulesets and related are released weekly (assuming we have any code in place to publish), while Core / CLI are released on demand using the approval workflow in CircleCI