chore(main): release 0.13.0

[C4illin]

🤖 I have created a release beep boop

0.13.0 (2025-04-24)

Features

• add HIDE_HISTORY option to control visibility of history page (bed52ce)
• add HIDE_HISTORY option to control visibility of history page (9d1c931)

Bug Fixes

• add timezone support (4b5c732), closes #258

---

This PR was generated with Release Please. See documentation.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request is a release PR that bumps the version of the convertx-frontend package from 0.12.1 to 0.13.0. It also updates the changelog to reflect the new release and includes a new feature that adds a HIDE_HISTORY option to control the visibility of the history page.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Bumped the version of the convertx-frontend package and updated the changelog.	Updated the version field in package.json from 0.12.1 to 0.13.0. Added a new entry to CHANGELOG.md for version 0.13.0, including a description of the new HIDE_HISTORY feature.	package.json CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @C4illin - I've reviewed your changes - here's some feedback:

Overall Comments:

• It looks like the same feature was added twice to the changelog - can you remove the duplicate entry?

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

question: Potential duplicate changelog entry

The changelog contains two identical entries for the HIDE_HISTORY option with different commit hashes. Please verify whether these are indeed separate commits or if one is redundant.