-
Notifications
You must be signed in to change notification settings - Fork 21
feat(dart): rely on common changelog #1788
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
Conversation
✅ Deploy Preview for api-clients-automation ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
do you want to make it retroactive @aallam |
We are still at alpha stage, we can just skip the old changelog content and start from new. |
true, I'll trigger a new release soon and delete previous content |
9925163
to
04a92a0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great !
} | ||
|
||
await updateChangelog(lang as Language, changelog[lang], current, next); | ||
await updateChangelog( | ||
lang as Language, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could be nice to use something like this to avoid the type conversion
will try it right away! |
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-1440
Changes included:
This PR aims at making Dart leverage the common changelog generation process, while still relying on Melos for version bump.
We now generate a changelog per Dart client, and omitting the changelog generation on the Melos side.
Things to fix:
currentVersion
from the Dart packageHow to test:
LOCAL_TEST_DEV=true
to your.env
file at the root of the repoyarn docker:release