CHANGELOG.md hasn't been updated since 2022

[phillco]

We have a few places where we put release notes:

• https://github.com/cursorless-dev/cursorless/tree/main/changelog (short entries for each PR, used to automatically generate release notes)
• https://www.cursorless.org/docs/user/release-notes/ (manually created / summarized posts)
• https://github.com/cursorless-dev/cursorless/blob/main/CHANGELOG.md (oldest)

However CHANGELOG.md is used on the marketplace:

and when you go to install an extension:

It's not entirely bad because usually this is also shown with the date of last release or the list of recent releases, which will obviously be fresher:

...but it probably causes people to miss new features or think the project is not as maintained as it otherwise is.

[AndreasArvidsson]

Any suggestions how to fix this?
Since the changelog markdown gets pulled into the marketplace that seems kinder important to keep up to date. Should we just use that and nothing else? Or maybe we should still use our purple request changes and then used a changelog markown as our release notes that we create periodically?

To be honest we haven't really been that good with doing release notes in the past and I'm not to optimistic about the future either. I'm more tempted to just use the changelog markdown and nothing else.

[phillco]

I'm happy to take on writing more of the release notes going forward, I like that kind of thing and I think it's good to get the maximal value for the work that all of the contributors have done.

[AndreasArvidsson]

Related issue #1795

As we talked about in one of the meetups you're very welcome to take the lead on this. I think we were in agreement that it would be best to put something in the pull request and then generate an manually edit changelog.md. Getting rid of the other sources for changes.

[pokey]

Update from quick chat with @AndreasArvidsson. For now, let's start with something simple just to get 1.0 out the door:

• we will just expect users to go to https://github.com/cursorless-dev/cursorless/tree/main/changelog. It is slightly awkward, but at least it is kept up-to-date
• We link to https://github.com/cursorless-dev/cursorless/tree/main/changelog from https://github.com/cursorless-dev/cursorless/blob/main/CHANGELOG.md, which is what is used by marketplace. We say something like Currently, we store changelog entries in [markdown blurbs in our monorepo](https://github.com/cursorless-dev/cursorless/blob/main/CHANGELOG.md). In the future, we'll generate snazzy release notes from these blurbs. Until then, you'll have to use your imagination
• We add a paragraph to https://github.com/cursorless-dev/cursorless/blob/main/packages/cursorless-org-docs/src/docs/user/release-notes/README.md saying Note that these release notes come out very occasionally, so if you want to know what we've been up to between releases, you can check out our raw changelog entries, which are stored in [markdown blurbs in our monorepo](https://github.com/cursorless-dev/cursorless/blob/main/CHANGELOG.md).In the future, we'll generate snazzy release notes from these blurbs. Until then, you'll have to use your imagination or wait for us to hand-write release notes
• We add a README.md to https://github.com/cursorless-dev/cursorless/tree/main/changelog saying This directory contains the raw changelog entries that we will one day use to generate snazzy release notes. Until then, you can read them here, imagining them in their beautiful future form

[AndreasArvidsson]

Here is the pull request for the above intermediate step.
#2856