Run yarn create rwjblue-release-it-setup

[fsmanuel]

To make the release process easier I run yarn create rwjblue-release-it-setup and fixed the repository.url in package.json.

[ijlee2]

I haven't used these and was surprised the amount of lines added to yarn.lock. To confirm, is the number of installed packages (resulting in about 3,000 changed LOC) expected?

Are there alternative release processes that we could consider?

[fsmanuel]

I was also very surprised. I think it's because the other dependencies are so outdated. I can reroll yarn.lock after the update in #87

I choose release-it because it's the recommanded way according to adopted-ember-addons guidelines

[ijlee2]

Ok. Yeah, following the recommended guidelines sounds good to me.

@buschtoens and I like to use yarn-deduplicate to maintain the lockfile and avoid installing multiple versions of a package. In #87, can you run these commands to see what happens?

# Check which packages could be de-duplicated
yarn-deduplicate --list

# De-duplicate packages
yarn-deduplicate && yarn

# Commit the lockfile (if there's a change)

Installation for yarn-deduplicate: https://www.npmjs.com/package/yarn-deduplicate

[fsmanuel]

Will do.

[ijlee2]

A good start. I find it nice to see an up-to-date changelog in an open-source package.

[fsmanuel]

@ijlee2 as mentioned in the comment above release-it is the standard for adopted-ember-addons. So I think it's a good idea to merge it and release v5.0 and have our first changelog entry created 🎉