generate changelog notes

[jshawl]

This PR adds an action step to generate the changelog notes for the latest JS SDK release:

For this demo, I added a step to the main.yml workflow to test it but moved it to publish.yml in 42ca4b3

[wsbrunson]

nothing blocking, this is looking really good

[wsbrunson]

does it make sense to do something like this to avoid the second loop?

Suggested change

	diff[dependency] = compareUrl(dependency, previous, current);
	}
	}
	for (let dependency in diff) {
	diff[dependency].changes = await getDiff(diff[dependency].api);
	}
	const urls = compareUrl(dependency, previous, current);
	diff[dependency] = {
	...urls,
	changes: await getDiff(urls.api)
	}
	}
	}

[wsbrunson]

you could do

Suggested change

	for (let dep in diff) {
	console.log(asciiDependencyDiff(dep, diff[dep].api));
	}
	for (const {api} of diff) {
	console.log(asciiDependencyDiff(dep, api));
	}

[wsbrunson]

same here

Suggested change

	for (let dep in diff) {
	console.log(`<${diff[dep].html}>`);
	diff[dep].changes.forEach((change) => {
	for (const {html, changes} in diff) {
	console.log(`<${html}>`);
	changes.forEach((change) => {

[jshawl]

excellent suggestions, thank you! I was thinking some more about this and am wondering if it might be better to keep the release notes generation out of sdk-release. e.g. it it's npm installable then releasers will be able to open a terminal and:

npx js-sdk-release-notes | pbcopy
# or
npx js-sdk-release-notes 5.0.432 | pbcopy
# or
npx js-sdk-release-notes 5.0.430...5.0.432 | pbcopy

[wsbrunson]

that would be really cool!

[wsbrunson]

one change i would consider is building up a string in your function and then doing console.log(result) instead of building it through console.log. may be easier said than done though so just a suggestion