chore: remove stale changesets clogging up release changelogs #399
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
The switch to the 2-branch model has led to stale changesets remaining in our
developbranch despite them getting properly cleaned out when cutting the release branch. We should address the workflow to properly clean these when cutting a release but for now let's just purge them manually.These changesets have been previously released in the
0.8.0and0.9.0releases. Still worth it to double check that I haven't removed any that are yet to be released