Version packages

[leoisadev1]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@opencoredev/mobbin-cli@0.1.1

Patch Changes

• c92d8d0: Set up Changesets, Depot validation, and npm Trusted Publishing release automation.

[greptile-apps]

Greptile Summary

This PR prepares the package for the 0.1.1 release.

• Removes the consumed Changesets release note.
• Adds the generated changelog entry for 0.1.1.
• Bumps package.json from 0.1.0 to 0.1.1.

Confidence Score: 5/5

The release metadata update is safe to merge.

The changes are limited to generated release bookkeeping: removing the consumed changeset, adding the changelog entry, and bumping the package version.

T-Rex Logs

What T-Rex did

• Captured the pre-change release package metadata log trex-artifacts/release-package-metadata-01-before.log to establish the baseline state.
• Captured the post-change release package metadata log trex-artifacts/release-package-metadata-02-after.log and confirmed the scripted checks exited 0 and reported PASS with the exact package version, presence of the changeset, and the changelog state.

_{Ran code and verified through T-Rex}

_{Reviews (4): Last reviewed commit: "Version packages" | Re-trigger Greptile}

[greptile-apps]

Release Commit Re-Triggers Workflow

When this version PR is merged, the changed CHANGELOG.md and package.json files match the release workflow's push paths. If that workflow does not explicitly skip version commits with no remaining changesets, the merge can start another release run that tries to open an empty version PR or publish the already-released package version.