Skip to content

Conversation

Kylejeong2
Copy link
Member

No description provided.

@Kylejeong2 Kylejeong2 closed this Aug 26, 2025
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greptile Summary

This PR reverts the changeset-based release automation that was previously added to the project. The revert removes all changeset tooling and infrastructure, rolling back from version 2.1.0 to 2.0.1 and returning to a simpler manual release process.

The changes affect multiple key areas:

  • Package configuration: The package.json is reverted to remove changeset scripts (changeset, version:packages, release), the @changesets/cli dev dependency, and the publishConfig section. The version is downgraded from 2.1.0 to 2.0.1.

  • Release automation: The complex .github/workflows/release.yml workflow that handled automated version bumping and changeset processing is completely removed. In its place, a simpler .github/workflows/publish.yml workflow is restored that only publishes to npm when GitHub releases are manually created.

  • Documentation: The CHANGELOG.md file is completely emptied, removing the 2.1.0 release notes that documented the changeset addition.

This revert indicates that the changeset implementation likely introduced complications with the release process or didn't integrate well with the project's workflow. The team is returning to a more traditional approach where releases are manually triggered through GitHub's release interface, which then automatically publishes to npm. This simplifies the release process by removing the automated version management and PR creation that changesets provided, but requires more manual intervention for releases.

Confidence score: 3/5

  • This PR requires careful review due to the removal of release infrastructure and potential version history complications
  • Score reflects concerns about the empty changelog creating confusion about release history and the need to verify the manual release process works correctly
  • Pay close attention to the workflow files and ensure the new publishing process is properly configured

Context used:

Context - We enforce linting and prettier at the CI level, so no code style comments that aren't obvious. (link)

4 files reviewed, no comments

Edit Code Review Bot Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant