Changeset in framework sometimes bumps with major instead of minor

## Description

When using changesets in the framework, version bumps occasionally use `major` instead of the expected `minor` version increment.

## Expected Behavior

Changeset should bump the version with a `minor` version increment when changes are not breaking.

## Actual Behavior

The changeset tooling sometimes incorrectly bumps the version as `major`, which can cause unintended breaking version signals to consumers.

## Steps to Reproduce

1. Create a changeset with a `minor` change
2. Run the changeset version command
3. Observe that the version is bumped as `major` instead of `minor`

## Possible Causes

- Incorrect changeset type set in the `.changeset` files
- Dependency resolution causing a cascade bump to `major`
- Misconfiguration in `changesets` config

## Additional Context

This issue should be investigated to understand the root cause and ensure consistent versioning behavior across the framework packages.