chore(changesets): remove changesets

[schultzp2020]

Description

We should remove the changesets from the showcase because we have not updated the changelogs since dev preview.

Which issue(s) does this PR fix

• Fixes https://issues.redhat.com/browse/RHIDP-1129

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f434f0

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.

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

[github-actions]

The image is available at: quay.io/janus-idp/backstage-showcase:pr-939!

[nickboldt]

Not to be too pedantic, but you're not removing the changesets...

they're still in https://github.com/janus-idp/backstage-showcase/tree/main/.changeset

you're just no longer checking PRs for new ones, and removing the yarn commands to add new ones.

FWIW this may be a different path to what's suggested for migrated plugins from backstage-plugins -> community-plugins as that team likes changesets (but we might convince them to do releases on every commit using semantic release instead or in addition to changeset-grouped releases).

[kadel]

Wouldn't it be better if we start using this properly instead of removing it? Last release we had a hard time coming up with the changelog, if we start using changesets properly it will make releases easier.

[kadel]

@schultzp2020 can you please rebase?
/approve

[kadel]

Wouldn't it be better if we start using this properly instead of removing it? Last release we had a hard time coming up with the changelog, if we start using changesets properly it will make releases easier.

we discussed that and come to the conclusion that we will remove changes fro now

[sonarcloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

The image is available at: quay.io/janus-idp/backstage-showcase:pr-939!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kadel, nickboldt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kadel,nickboldt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment