-
-
Notifications
You must be signed in to change notification settings - Fork 944
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
Setup release-it
+ changelog plugin
#1096
Labels
Milestone
Comments
Shinigami92
added
c: refactor
PR that affects the runtime behavior, but doesn't add new features or fixes bugs
breaking change
Cannot be merged when next version is not a major release
labels
Jun 20, 2022
See also #942 |
Today I will try https://github.com/release-it/release-it with some of my personal repos |
Shinigami92
changed the title
Replace
Replace Oct 7, 2022
standard-version
with changesets
standard-version
with alternative
Shinigami92
changed the title
Replace
Setup Oct 13, 2022
standard-version
with alternativerelease-it
+ changelog plugin
Shinigami92
added
p: 1-normal
Nothing urgent
c: infra
Changes to our infrastructure or project setup
and removed
c: refactor
PR that affects the runtime behavior, but doesn't add new features or fixes bugs
breaking change
Cannot be merged when next version is not a major release
labels
Oct 15, 2022
Team Decision We don't need this for v8.0. |
ST-DDT
modified the milestones:
v8.0 - Module Re-Shuffling,
v8 - None milestone specific tasks
Apr 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Replace https://github.com/conventional-changelog/standard-version with https://github.com/changesets/changesets
standard-version
is deprecated and not maintained anymore: see https://www.npmjs.com/package/standard-versionThe author suggests to use https://github.com/googleapis/release-please
We could look into that, but I would suggest to have a look into
changesets
as it is used by pnpmAs changing the release process might produce a different style of
CHANGELOG.md
, I would prefer to make the move to a new release workflow in a major update of Faker.changesets
can definitely handle mono-repos and maybe someday we want to convert this repo to a monorepo, so when suggesting alternative tools or workflows, keep this in mind.related to #268
The text was updated successfully, but these errors were encountered: