Using changesets to update Announcement.tsx

[a8trejo]

Description

Using changesets to update Announcement.tsx

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist:

• My code follows the patterns of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Additional context

Related Issues

Reviewers

---

Important

Automate updates to Announcement.tsx and latestAnnouncementId in ClineProvider.ts using new scripts and modify workflow to run these scripts for major/minor version changes.

• Scripts:
  • Add update-announcement-id.py to update latestAnnouncementId in ClineProvider.ts.
  • Add update-announcement.js to update Announcement.tsx with latest changelog entry.
• Workflow:
  • Modify changeset-release.yml to run new scripts for major/minor version changes.
  • Add step to format Announcement.tsx using Prettier.
• Components:
  • Update Announcement.tsx to use full version number.
• Misc:
  • Add markdown-to-jsx dependency in package.json.

^{This description was created by for 9a78b05. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9a78b05

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

Consider adding error handling for the case where the VERSION environment variable is not set to prevent a KeyError.

[ellipsis-dev]

The line formattedContent.replace('{" "}', "") does not modify formattedContent as strings are immutable. Consider reassigning the result to formattedContent.

[mrubens]

Heads up that I ran prettier on the whole codebase in #404, and it will run automatically in a pre-commit hook going forward.

In order to bring this PR up to date on formatting you'll need to run npx prettier './**/*.{js,jsx,ts,tsx,json,css,md}' --write. Sorry for any hassle with this, and let me know if you get stuck!